Add helper for detecting if the current device is a mobile viewport

[Chucks1093]

Summary

Several UI decisions (tooltip vs toast, collapsed vs expanded nav) depend on whether the user is on a mobile viewport. A shared helper that reads the window width and returns a boolean should be used consistently instead of inline media query checks scattered across components.

Scope

• Add useIsMobile(): boolean React hook using a window.matchMedia listener with a 768px breakpoint
• Hook updates correctly when the viewport is resized
• Cleans up the media query listener on unmount
• Add unit tests mocking window.matchMedia for mobile and desktop widths

Acceptance Criteria

• Returns true for viewport width below 768px
• Returns false for viewport width at or above 768px
• Updates correctly on viewport resize
• Listener is cleaned up on unmount

ETA: 12 hours

---

Coordinate on Telegram

[egwujiohaifesinachiperpetual-max]

@egwujiohaifesinachiperpetual-max has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

please assign to me my ETA is 4hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @egwujiohaifesinachiperpetual-max to this issue.

[Richardkingz2019]

@Richardkingz2019 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Richardkingz2019 to this issue.

[archanavdev]

@archanavdev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @archanavdev to this issue.

[drips-wave]

Congratulations, @archanavdev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @archanavdev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @archanavdev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #481)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@archanavdev's PR #513 was approved and merged by @Chucks1093.

🏆 @archanavdev: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (293 total points). Track your full progress on GrantFox.

👏 Great work, @archanavdev! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @archanavdev as part of the Stellar Wave Program's 6th Wave 🥳

😎 @archanavdev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.