Role-Specific Home Dashboard

medium complexity MVP extracted Home & Navigation Confidence: 100%

Components

Shared

User Stories

Yes

Analyzed

Description

The Role-Specific Home Dashboard is the primary landing screen, rendering relevant widgets and quick actions based on the authenticated user role. Peer Mentors see their activities and contacts; Coordinators see team summaries and pending approvals. Navigation items and home widgets are assembled at runtime from the enabled module set, ensuring no hardcoded org branches in the widget tree. All elements meet WCAG 2.2 AA touch target and screen reader requirements from day one.

Sources & reasoning

Source explicitly names role-specific home content and module-registry-driven assembly as foundational mobile architecture. Fase 1 confirms two mobile role profiles must be supported from MVP. The blueprint assigns MVP, matching the first-phase ordinal. This feature is architecturally load-bearing for all multi-tenant functionality.

No source references — this artifact was included based on reasoning alone (see above).

Analysis

Business Value

The home screen is the first view every user encounters after login, making it decisive for adoption and daily engagement. A role-specific view reduces cognitive load by surfacing only relevant actions - critical for peer mentors with limited digital experience. For coordinators, immediate team visibility reduces administrative overhead. The module-registry-driven assembly means new organizations onboard with different capability sets without code changes. This directly supports the top design principle of minimizing cognitive load stated as the highest priority across all four organizations.

Implementation Notes

The home screen is driven by the Module Registry Service, which reads the enabled module set from the backend bootstrap. Each area registers its home widgets against its area ID; the screen mounts only widgets for enabled modules. Role differentiation uses Riverpod: the active role provider drives which widget variants render. A HomeViewModel combines registry state and role context into a single state object. All widgets must meet WCAG 2.2 AA touch targets with semantic labels for VoiceOver and TalkBack. Role switching must update the home screen without resetting the navigation stack.