Notes List
Feature Detail
Description
The Notes List feature provides peer mentors and coordinators with a structured overview of all notes they have created within the app. Notes are tied to contacts or activities and serve as a lightweight journal for tracking observations, follow-up items, and contextual information that does not fit the structured activity log. The list view supports search and sorting so users can quickly locate relevant entries across potentially large collections. This feature is the entry point for the entire notes module and must load efficiently even on slow connections, relying on the offline-first architecture (Drift + SQLCipher) to surface cached notes instantly while syncing in the background. WCAG 2.2 AA compliance is required from day one, including sufficient touch targets and full screen-reader support.
Analysis
Notes give peer mentors a private, structured space to record observations and follow-up intentions that fall outside formal activity registration. Without this, contextual knowledge lives in personal notebooks or memory, creating continuity risk when a coordinator needs to step in or when a peer mentor resumes contact after a break. Providing an in-app notes list removes that risk and keeps all relevant information within a single, GDPR-compliant system. From an organizational perspective, notes reduce the cognitive load on peer mentors by giving them a trusted place to capture information immediately after an interaction. This supports the core design principle of minimal cognitive burden articulated in the workshop findings, and indirectly improves the quality and completeness of formal activity reporting by ensuring nothing is forgotten between an interaction and its registration.
The notes list is implemented as a Riverpod-managed screen in Flutter, backed by a Drift DAO that queries the notes table filtered by the current user. Pagination or lazy loading should be used to handle users with hundreds of notes without degrading scroll performance. Search is client-side for offline support, filtering by note title or body text in the local SQLite database. The list must integrate with the offline-first sync layer: notes created offline are held in the mutation outbox and synced via the background sync queue. List items display creation date, associated contact name (if any), and a truncated preview of the note body. The screen uses the shared design token system for typography and spacing, and all interactive elements meet WCAG 2.2 AA target size requirements (minimum 24x24 CSS pixels equivalent).
Components (42)
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.