Profile Data & Settings

Accurate user profiles are foundational to the platform's trust and reporting integrity. Peer mentors and coordinators need a reliable self-service way to keep their contact details current without administrator intervention, reducing admin burden and support requests. For organizations like NHF that serve users with cognitive challenges including stroke survivors, a well-designed profile screen with clear affordances directly supports the platform's accessibility commitment. Errors in profile data can cascade into reporting inaccuracies that affect Bufdir submissions. Providing in-app profile editing also reduces dependency on manual onboarding corrections by Org Admins, accelerating time-to-value for new users across all five organizations.

Implement as a Flutter screen using Riverpod for state management. Form fields should use the shared AppTextField widget with real-time validation. Profile reads and writes go through a dedicated ProfileService hitting the REST API; optimistic updates with rollback keep the UX snappy on slow connections. The screen must satisfy WCAG 2.2 AA: minimum 4.5:1 text contrast, 24x24 px touch targets, visible focus indicators, and semantic labels on all fields. Drift local DB caches the profile for offline display; writes are queued in the mutation outbox when offline. Organization labels (e.g. overridden role terms) should be applied when rendering role-related profile fields, fetched from the backend labels cache.