Refactor mobile app state management to use context + hooks pattern

[Smartdevs17]

Context

State management needs modernization with context and hooks.

Current Limitation

State management uses mixed patterns.

Expected Outcome

• Consistent context + hooks pattern
• Reduced prop drilling
• Improved testability
• Better TypeScript inference

Acceptance Criteria

• Context providers for global state
• Custom hooks for state access
• Reduced prop drilling
• Improved testability
• Better TypeScript inference
• Performance benchmarks
• Migration documentation

Technical Scope

• src/store/ - Zustand stores
• src/context/ - React contexts
• src/hooks/ - Custom hooks
• src/components/ - Component integration

[MoscowDev]

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

I'd be happy to take this issue on. I have experience building production-ready applications and collaborating effectively through GitHub workflows, including implementing features, resolving bugs, and submitting well-documented pull requests.

I'll carefully review the existing implementation, identify the root cause, and deliver a robust, maintainable solution that aligns with the project's architecture and coding standards. Before submitting my PR, I'll thoroughly test the changes to ensure reliability and avoid regressions.

My goal is to contribute high-quality, clean, and maintainable code while communicating clearly throughout the process and delivering a dependable solution in a timely manner.

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

[garfieldxxx1]

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

This is something I can do
I would love this task assigned to me

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

[Netty-kun]

@Netty-kun has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue. I've gone through the details and understand what's needed to resolve it. Since I've implemented similar changes before, I should be able to deliver a PR within 48 hours, possibly earlier if I can get started soon.

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

[Itodo-S]

@Itodo-S has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please let me work on this issue; I can handle it

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

[drips-wave]

Congratulations, @Itodo-S! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Itodo-S: 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 🌊

[Itodo-S]

Fixed in PR #828: #828

[drips-wave]

This issue has been completed by @Itodo-S as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Itodo-S: 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.