FAQ
Feature Detail
Description
The FAQ screen provides a searchable, categorized list of frequently asked questions covering core workflows: activity registration, expense submission, contact management, and common error scenarios. Questions are organized by role (Peer Mentor vs Coordinator) and filterable by keyword. The screen supports offline access with cached content and is designed for cognitive accessibility - short plain-language answers and an accordion layout that reduces visual clutter for users with varying digital skill levels.
Sources & reasoning
The cognitive accessibility emphasis (§1.2) and the parallel-systems transition philosophy (§1.5) both point to a self-service guidance need. Users unfamiliar with the app need answers without contacting support. The blueprint marks this MVP under the always-on help-support module. Section §1.5 frames the app as an offer not a mandate, implying low-friction onboarding - a searchable FAQ with role-organized entries directly supports this.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
The Meander platform targets volunteers including elderly users, stroke survivors, and individuals with cognitive challenges, many of whom need guidance beyond what the UI itself communicates. A well-structured FAQ reduces support overhead for Norse Digital Products and for coordinators who currently act as informal help desks for peer mentors. During the parallel-systems transition, a FAQ mapping old Word and Excel workflows to new in-app flows will directly reduce adoption resistance. The feature has low implementation cost relative to its support deflection value and is a standard expectation for any professional mobile product targeting non-technical users across four organizations with different onboarding needs.
Implemented as a Flutter screen backed by a JSON dataset fetched from the backend and cached locally for offline access. Entries are structured with question, answer, category tag, and role filter (peer_mentor, coordinator, all). Search runs client-side against cached data using substring matching. The accordion/expansion tile pattern keeps answers hidden until tapped, reducing visual clutter. WCAG 2.2 AA compliance required: expansion controls must have semantic labels and meet touch target size requirements. Content is managed via a backend endpoint so FAQ entries can be updated without an app release as post-launch questions emerge from user feedback across the four organizations.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.