FAQ
Feature Detail
Description
The FAQ feature provides a searchable, categorized list of frequently asked questions covering common user journeys — activity registration, expense submission, role management, and technical troubleshooting. Questions and answers are maintained by administrators via the admin portal and served to the mobile app through a backend API, allowing content updates without app releases. The FAQ reduces support load by enabling self-service resolution of common issues and is particularly important for onboarding users with limited digital experience.
User Flow
Analysis
The target user base includes peer mentors with beginner-level digital skills, elderly users, and users with cognitive or sensory impairments across four partner organizations with different workflows. A well-maintained FAQ reduces inbound support volume, lowers the cost of scaling the platform to new organizations, and empowers users to resolve issues independently at any time — including outside business hours when coordinators are unavailable. For Norse Digital Products, a centralized FAQ that can be updated without an app release provides operational agility: when onboarding a new organization or releasing a new feature, relevant guidance can be published immediately. Reducing support friction also directly improves activity registration rates, which is the primary KPI for all partner organizations.
The FAQ is backed by a `faq_items` table in PostgreSQL storing question, answer, category, sort order, and product/role targeting fields. The Next.js API exposes a paginated GET endpoint filtered by product (mobile) and optionally by user role. The Flutter client renders a searchable list grouped by category, with expand/collapse per item. Search is implemented client-side over the fetched dataset for offline resilience, with a fallback to API search for large datasets. All content must be accessible: expandable items must use proper ARIA expanded/collapsed states, search input must have a visible label, and the list must support keyboard and switch access navigation. Admins manage FAQ content through a simple CRUD interface in the admin portal. Content should support basic markdown for formatting answers.
Components (112)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.