Restructure mobile app navigation to use feature-based modular architecture

[Smartdevs17]

Context

React Navigation is organized as a single flat navigator with all 54+ screens registered centrally, causing merge conflicts and tight coupling.

Current Limitation/Problem

Adding a new screen requires modifying the central navigation file. Feature teams create merge conflicts on the same navigation file regularly.

Expected Outcome

Feature-based navigation: each domain module owns its navigator stack. Root navigator composes feature navigators. Each feature defines its own param list type.

Acceptance Criteria

• Each feature has its own Navigator component: AuthNavigator, BillingNavigator, SubscriptionNavigator, SettingsNavigator, AdminNavigator
• Root navigator uses composition pattern: render feature navigators as screens
• Deep linking: deeplink patterns (subtrackr://subscriptions/123) map to correct feature navigator
• Type-safe navigation: each feature defines its own ParamList type, exported and consumed by root
• No circular type dependencies between features enforced by ESLint rule
• Migration: all existing 54+ screens moved without behavior change
• Performance: no increase in navigation mount time (measured <100ms for initial render)

Technical Scope

• mobile/app/navigation/ - RootNavigator with feature composition
• mobile/features/auth/navigation/ - AuthNavigator
• mobile/features/billing/navigation/ - BillingNavigator
• mobile/features/subscriptions/navigation/ - SubscriptionNavigator
• mobile/features/settings/navigation/ - SettingsNavigator
• mobile/features/admin/navigation/ - AdminNavigator
• shared/types/navigation.ts - root param list type

[Frontman-Code]

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

will love to work on it

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

[debbieAmoni]

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

hello maintainer i would love to work on this issue , i can work on it immediately

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

[drips-wave]

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

🧑‍💻 @Frontman-Code: 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 🌊