Profile Data & Settings

medium complexity extracted Profile Management Confidence: 100%

Components

Shared

User Stories

Yes

Analyzed

Description

Profile Data & Settings is the core identity management feature for peer mentors and coordinators within the Meander mobile app. It allows users to view and edit their personal information, including name, contact details, profile photo, language preferences, and any organization-specific fields. The screen acts as the single place where a user manages how they appear to coordinators, other peer mentors, and the system. The feature also covers app-level preferences such as notification defaults and accessibility settings. Because Meander serves users with varying cognitive and motor abilities, all form fields must meet WCAG 2.2 AA requirements: adequate touch targets, screen-reader labels, clear error messages, and scalable typography. Changes are persisted both locally (Drift offline cache) and to the backend REST API, with optimistic updates and automatic rollback on failure.

Analysis

Business Value

Accurate user profiles are foundational to every downstream workflow in the platform. Coordinators rely on profile data to assign peer mentors to contacts, validate reimbursement claims, and produce Bufdir reports. Without a reliable, self-service profile editing flow, coordinators bear the administrative burden of correcting data manually - increasing overhead and introducing errors in official reporting. For peer mentors, the ability to maintain their own profile fosters autonomy and reduces friction. Multi-organization users (e.g. members of up to five NHF local chapters) must be able to see which organizations they belong to without confusion. Accessible profile editing also directly supports the platform's WCAG 2.2 AA commitment, which is a contractual requirement for all participating organizations, not an enhancement.

Implementation Notes

The Profile Screen and Profile Edit Screen are separate routes: the detail view is read-only with an Edit button, preventing accidental mutations. Form state is managed with Riverpod (no codegen), using a dedicated ProfileEditNotifier that tracks dirty state and validates fields before submission. The Users Table is the canonical backend store; the mobile app syncs via PATCH /api/v1/users/{id}. Offline support uses Drift: the local users table is updated optimistically, and the mutation outbox queues the PATCH if the device is offline. On reconnect the sync queue replays the mutation and resolves any conflict by last-writer-wins for non-critical fields. All text inputs use Flutter's Semantics widget with explicit labels; error states announce via live region for screen-reader compatibility.