Simple Activity Logging
Feature Detail
Description
Simple Activity Logging provides peer mentors with a minimal-friction interface to record interactions with contacts. The system uses intelligent defaults (today's date, 30-minute duration) that can be overridden, targeting completion in under two clicks for the most common case. This addresses the universal top-priority need identified across all four organizations, where current paper and Word-based workflows cause massive underreporting because the process is too cumbersome for volunteers to complete consistently.
Sources & reasoning
All four organizations named this the top-priority function (line 14-18). The 30-min default, under-two-clicks target, and HLF's 380-registration example (lines 20-22) directly define the UX contract. Phase matrix marks it Fase 1 / MUST HAVE, mapping to MVP.
-
docs/source/likeperson.md · line 20-22NHF: Word-skjemaer sendes manuelt til regioner → manuell Excel-aggregering sentralt. Mål: registrering på under to klikk.
-
docs/source/likeperson.md · line 22HLF: En likeperson hadde 380 enkeltregistreringer på ett år. Standardverdier (dagens dato, 30 min) som kan overstyres.
-
docs/source/likeperson.md · line 24Designprinsipp: Lavest mulig kognitiv belastning. Standardvalg, gjenkjennelig logikk, færrest mulig steg.
Analysis
All four partner organizations identified simple activity logging as their single highest-priority requirement, describing current manual processes as unsustainable. NHF uses Word forms with manual Excel aggregation; HLF reported one peer mentor with 380 individual registrations in a year using the old system. Underreporting directly undermines Bufdir grant reporting, which funds the programs. Every additional tap or form field correlates with lower compliance rates among volunteers with beginner digital skills. Reducing cognitive load to the absolute minimum is the defining business constraint for this feature and for the platform as a whole.
Implement as a Flutter widget using Riverpod state management with pre-populated defaults injected at screen construction. The ActivityService posts to REST API with optimistic mutation and automatic rollback on failure. Drift offline database stores pending mutations in the outbox queue with retry/backoff. Form validation must be WCAG 2.2 AA compliant with minimum 24x24 touch targets and 4.5:1 contrast. Low temperature AI prompting (0.1) for any AI-assisted fields. The ActivityRepository handles conflict resolution when the same activity is submitted offline and later synced.
Quality Assurance
No QA section has been generated for this feature yet.
Components (21)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.