Calendar Sync

medium complexity MVP extracted Activity Registration Confidence: 100%

Components

Shared

User Stories

Yes

Analyzed

Description

Calendar Sync integrates the Meander mobile app with the device's native calendar on iOS and Android, allowing peer mentors to have scheduled activities and events appear alongside their personal commitments. After granting calendar permission, new activities and events are written as calendar entries, giving users system-level reminders without requiring the app to be open. A dedicated infrastructure component handles the OS-level permission rationale and runtime request on both platforms.

Sources & reasoning

HLF's survey data on follow-up dissatisfaction directly motivates calendar sync as a lightweight reminder mechanism. The feature appears in the Fase 2 context through HLF unique needs (§3.3) and is corroborated by the Fase 2 action list (§7), mapping to v1.0 by ordinal phase position.

No source references — this artifact was included based on reasoning alone (see above).

Analysis

Business Value

HLF's workshop explicitly cited poor follow-up satisfaction - 40% of peer mentors were unsatisfied according to a survey - and named calendar synchronization as a direct mechanism for improvement. Surfacing activities in the native calendar means peer mentors receive OS-level reminders for upcoming visits without relying on in-app notifications alone, reducing missed follow-ups and the coordinator effort required to chase outstanding records. For organizations managing large numbers of peer mentors, higher follow-through rates on scheduled activities directly improve data completeness in Bufdir reports and reduce coordinator overhead.

Implementation Notes

Uses a Flutter device calendar plugin (e.g., device_calendar) to write calendar entries after the user grants permission. The CalendarPermission Handler infrastructure component presents an in-app rationale screen before triggering the OS dialog on both iOS and Android, following platform guidelines for permission request timing. Calendar entries are created on activity or event save and updated on edit; deletion from the app optionally removes the corresponding calendar entry. Sync is one-directional (app → device calendar) at v1.0 to avoid the conflict-resolution complexity of bi-directional sync. The feature is guarded by the module toggle system and disabled by default.