Simple Activity Logging
Feature Detail
Description
Simple Activity Logging enables peer mentors to record interactions with contacts in the fewest possible steps. The feature provides smart defaults - today's date and 30-minute duration - covering the majority of use cases, allowing most registrations to complete in under two clicks. This directly addresses the underreporting problem where volunteers skip logging because existing processes are too cumbersome, protecting Bufdir funding and organizational reporting accuracy.
Sources & reasoning
All four organizations named activity logging their top priority; line 18 identifies systemic underreporting as the core problem; line 22 demonstrates scale (380 registrations/year); line 24 establishes the minimal cognitive load design principle. Blueprint assigns [MVP] matching the Fase 1 roadmap mandate for 'Aktivitetsregistrering med lavest mulig antall klikk'.
-
docs/source/likeperson.md · line 18Fellesnevneren er at rapporteringen er så tungvint at det fører til massiv underrapportering - enten fordi folk ikke orker, eller fordi de ikke engang skjønner at det de gjør teller.
-
docs/source/likeperson.md · line 22En likeperson hadde 380 enkeltregistreringer på ett år. Standardverdier (dagens dato, 30 min) som kan overstyres. 60-70 % av registreringene er uten refusjon og skal være ekstremt enkle.
-
docs/source/likeperson.md · line 24Designprinsipp: Lavest mulig kognitiv belastning. Standardvalg, gjenkjennelig logikk, færrest mulig steg.
Analysis
All four partner organizations named simple activity logging their single most important feature, describing the current situation as unsustainable. HLF reports one peer mentor with 380 registrations in a year, making frictionless logging essential. Underreporting caused by complex processes directly threatens Bufdir funding all organizations depend on. By reducing registration to under two clicks with intelligent defaults, this feature increases data completeness and ensures funding accuracy. It is the foundational capability on which the entire platform's value proposition rests.
Implementation uses Flutter with Bloc/Riverpod state management. The quick-log form pre-fills today's date and 30-minute duration, with minimal required fields (contact, activity type, date, duration). ActivityService validates input and ActivityRepository persists data via Drift with SQLCipher encryption. Mutations queue in the offline outbox and sync when connectivity resumes. WCAG 2.2 AA requires 24x24px touch targets, 4.5:1 contrast, and semantic labels on all elements. Fixed activity type options prevent invalid combinations and reduce cognitive load.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.