Role-Specific Home Dashboard
Feature Detail
Description
The Role-Specific Home Dashboard provides a tailored entry point for each user role upon login, assembling the home screen dynamically from the enabled module set returned by the backend rather than hardcoding per-organization layouts. Peer Mentors see their recent activity summary, quick-log shortcuts, upcoming events, and relevant notifications, while Coordinators see a team overview, pending approvals, and assignment status. The bottom navigation bar with five tabs (Home, Contacts, Add, Work, Notifications) is rendered here and adapts to the role and enabled modules. The Module Registry Service drives which widgets and nav entries are mounted at runtime, ensuring no compile-time switching per organization is required.
Analysis
A role-appropriate home screen dramatically reduces cognitive load for peer mentors, who are assumed to have beginner-level digital skills, by surfacing only the actions and data relevant to their daily work. For coordinators it consolidates oversight tasks that would otherwise require navigating multiple screens. This directness is a primary driver of adoption - particularly for NHF users with cognitive or motor challenges - and directly supports the platform-wide principle of minimum clicks and maximum clarity. The runtime module assembly means new organizations can onboard by toggling modules without a new app release, protecting the commercial roadmap and reducing release overhead for Norse Digital Products. A well-designed home also anchors the brand experience that the sales website promises prospective customers.
Implement using Flutter with Riverpod (no codegen). The Module Registry Service reads the enabled module set from the bootstrap API response and exposes a stream of active nav items and home widgets; the home screen and bottom nav bar subscribe to this stream. Each area registers its nav item, home widget, and deep-link routes against its area ID at app startup using a declarative registry pattern - disabled areas are simply not mounted. Role detection comes from the JWT claims bag; the home screen selects the correct widget set (PeerMentorHomeScreen vs CoordinatorHomeScreen) based on role without branching per organization. The bottom nav bar must meet WCAG 2.2 AA touch target minimums (48x48 logical pixels recommended) and carry semantic labels for VoiceOver. Offline support via Drift ensures the home screen renders meaningful cached data when connectivity is absent.
Components (41)
Shared Components
These components are reused across multiple features
User Interface (9)
Service Layer (15)
Data Layer (8)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.