Event Creation
Feature Detail
Description
This feature enables peer mentors and coordinators to create structured events within the Meander Mobile App using a multi-step wizard flow. The wizard guides the user through defining an event title, date, time, duration, location, and a summary before submission. The flow mirrors the activity registration wizard pattern, minimising cognitive load by breaking the task into discrete, sequential steps with sensible defaults. Events differ from activities in that they represent group or scheduled occurrences rather than individual one-to-one interactions. The creation flow validates each step before advancing, surfacing clear inline errors. All interactive elements meet WCAG 2.2 AA requirements including minimum touch targets, semantic labels, and visible focus indicators.
Sources & reasoning
The source doc explicitly names an Event wizard in the core mobile navigation (lines 289-296) as part of the Add modal launcher, placing it alongside activity registration in the baseline app shell. The blueprint assigns [MVP] to Event Creation. The navigation description treats events as a first-class creation surface from launch, confirming MVP target.
-
docs/source/likeperson.md · line 289-296Bottom nav with 5 tabs: Home, Contacts, Add (modal launcher for Activity and Event wizards), Work, Notifications … Event wizard (multi-step: title → date → time → duration → location → summary)
Analysis
Group events are a core activity type for peer mentor organisations - coordinators regularly run workshops, training days, and group support sessions that a single-activity log cannot adequately represent. Without structured event creation, these activities are either unrecorded or shoehorned into individual activity entries, degrading reporting accuracy for Bufdir submissions and internal statistics. Providing a dedicated creation wizard directly addresses the universal requirement for low-friction registration identified across all four organisations. Events captured here feed coordinator dashboards, team reports, and the Bufdir export pipeline, making the feature load-bearing for downstream reporting and grant compliance.
Implemented as a multi-step Flutter BLoC wizard matching the activity wizard pattern: CreateEventScreen hosts a step controller that drives WizardStepTitle, WizardStepDateTime, WizardStepDuration, WizardStepLocation, and WizardStepSummary screens. Each step validates locally before emitting a transition event. The final step posts to the REST API via ApiHttpClient with JWT bearer; on 401 the client auto-refreshes the token before retrying. Offline-first: new events are written to the Drift local database and the mutation outbox immediately, then synced by SyncQueueService when connectivity is restored. EventRepository manages local CRUD and ID mapping for offline-created entities. The EventService coordinates wizard state, submission, and conflict resolution.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.