medium complexity extracted Home & Navigation Confidence: 100%
6
Components
4
Shared
0
User Stories
Yes
Analyzed

Description

The Role-Specific Home Dashboard delivers a personalized entry screen tailored to each user's role within the Meander platform. Peer Mentors see their own activity summary and upcoming tasks, while Coordinators see a team overview with pending approvals and alerts. The dashboard assembles its content at runtime from the enabled module set, ensuring only relevant widgets are mounted. This is a non-negotiable MVP surface that gives users immediate orientation and anchors the module registry navigation system for the entire application.

Sources & reasoning

Line 293 names role-specific home content as a screen. Line 240 classifies home-navigation as always-on core, making this non-deferrable. Line 322 confirms MVP scope includes both Peer Mentor and Coordinator roles. Line 308 ties the home surface directly to the module registry, confirming MVP target release.

  • docs/source/likeperson.md · line 293
    Role-specific home content (peer mentor vs coordinator variants)
  • docs/source/likeperson.md · line 240
    **Mobile App:** `authentication-access-control`, `home-navigation`, `accessibility`, `help-support`, `profile-management`.
  • docs/source/likeperson.md · line 322
    2 mobilrolle-profiler: Peer Mentor, Coordinator (Organization Admins logger på som Coordinator i app-konteksten)
  • docs/source/likeperson.md · line 308
    Module registry - the app's navigation, home surfaces, and entry points are assembled at runtime from the enabled module set

Analysis

Business Value

The home dashboard is the primary touchpoint users encounter after login, making it the most critical surface for adoption and daily engagement. A role-appropriate entry point reduces cognitive load for users with varying digital skill levels, which is especially important given NHF's focus on cognitively accessible design for stroke survivors and persons with cognitive challenges. Coordinators benefit from immediate team-level visibility without navigating multiple screens. The dashboard also anchors the module registry: it is the surface from which navigation items for enabled areas are mounted at runtime, making it foundational to the platform's multi-tenant, module-toggle architecture and impossible to defer.

Implementation Notes

Built in Flutter with Riverpod state management, the dashboard switches widget trees based on the authenticated user's role claim from the JWT. ModuleRegistryService fetches the enabled module set from the backend bootstrap response and injects it into home widget assembly at startup. Separate PeerMentorHomeScreen and CoordinatorHomeScreen widgets isolate role-specific logic. Offline support via Drift means the last-known dashboard state is shown immediately on cold launch. WCAG 2.2 AA compliance requires semantic labels on all interactive home elements, a minimum 4.5:1 contrast ratio, and visible focus indicators throughout the screen.

User Stories

No user stories have been generated for this feature yet.