Access Profile Screen via Bottom Navigation
The peer mentor profile screen must be easily accessible from the main app navigation. Based on the current architecture using a 5-tab bottom navigation (Home, Contacts, Add, Work, Notifications), the profile should be accessible either as a tab or from the Home screen's quick-action area. The navigation should preserve tab state using StatefulShellRoute so returning to the profile does not force a full reload. The profile screen must be accessible with a maximum of 2 taps from any tab. This story focuses on the navigation integration aspect of the profile screen implementation.
User Story
Audience Summaries
Frictionless navigation is a proven driver of feature adoption. If peer mentors cannot reach their profile in two taps or less, the self-management hub becomes an unused feature, eroding the ROI of the entire certification and availability workflow. This story ensures the profile screen is a first-class destination within the 5-tab navigation architecture, directly increasing the likelihood that mentors proactively monitor their certification health and pause status. Higher proactive engagement reduces administrative overhead for chapter coordinators, cuts the volume of reactive support requests, and protects the organization from compliance gaps caused by mentors who were simply unaware of their status.
Volunteer retention also improves when the app feels polished and effortless, supporting long-term program sustainability.
This story has medium complexity but is a blocking dependency for all profile-screen user stories. Delivery requires coordination between the routing layer (StatefulShellRoute configuration), the home screen quick-action area, and the peer-mentor-detail-screen-widget. The primary acceptance criteria — reachable in at most 2 taps from any tab, with preserved scroll and panel state on return — must be validated across all 5 navigation tabs. UAT should include back-button behaviour on both iOS and Android, which historically surfaces platform-specific edge cases.
Effort estimate should account for state preservation testing across navigation paths. Risk: if StatefulShellRoute is not already implemented in the router, setup time adds scope. Confirm router architecture with the mobile lead before sprint planning to avoid mid-sprint blockers.
Implementation centers on integrating the profile screen into the existing GoRouter StatefulShellRoute configuration so that tab state is preserved across navigations. The profile access point must be wired from both a dedicated tab slot (or Home screen quick-action widget) and must resolve to the full peer-mentor-detail-screen-widget. Key tasks: (1) add or confirm StatefulShellRoute branch for profile, (2) wire the Home screen quick-action tap handler to push the profile route, (3) ensure all data panels within the profile widget use concurrent Future.wait or parallel provider fetches to minimize perceived load time on first entry. Edge cases: back-button on Android must pop to the originating tab without resetting profile state; deep-link entry must not bypass the navigation shell.
Write widget tests covering the 2-tap constraint from each of the 5 tabs and a back-navigation test asserting scroll position retention.
Acceptance Criteria
- Given I am on any tab in the app, When I navigate to my profile screen, Then I can reach it in at most 2 taps
- Given I am on my profile screen and navigate to another tab, When I navigate back to the profile, Then the profile screen state is preserved (scroll position, expanded panels)
- Given I tap the profile access point from the home screen, When navigation occurs, Then the full peer-mentor-detail-screen-widget loads with all panels visible
- Given I am on the profile screen, When I press the system back button, Then I return to the previous screen without the profile losing its loaded state
- Given the app has just launched and I navigate to my profile, When the screen loads, Then all panels load their data concurrently to minimize perceived load time
Business Value
Navigation friction directly impacts feature adoption. If peer mentors cannot quickly access their profile and status screen, they will not proactively monitor certifications or pause status. Easy access is essential for the profile to serve its purpose as a self-management hub. This story ensures the profile is a first-class destination in the app navigation architecture.
Components
- Peer Mentor Detail Screen ui
- Peer Mentor Detail BLoC service
- Role-Based Home Screen ui
- Role-Aware Bottom Navigation ui
- Design Token Theme infrastructure