Roadmap: FamilySync

Overview

FamilySync is built in five phases, each delivering an end-to-end user-observable capability. Phase 1 is both the foundation and the highest-risk gate: OIDC auth must work and the CalDAV broker must prove it can read personal Fastmail calendars before any calendar UI is built. Phases 2–3 complete the calendar. Phase 4 delivers shared lists with live co-edit sync. Phase 5 wires up Web Push notifications. The dependency chain is strict: each phase is a prerequisite for the next, except the lists track (Phase 4) which is independent of the calendar write path.

Phases

Phase Numbering:

Integer phases (1, 2, 3): Planned milestone work
Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)

Decimal phases appear between their surrounding integers in numeric order.

Phase 1: Foundation + Broker Spike - Auth, Docker scaffold, CalDAV broker read path, and personal-calendar ACL spike (go/no-go gate)
Phase 2: Calendar Display - Read-only unified color-coded calendar (week/month/day/agenda) built on the confirmed broker
Phase 3: Event Write-Back + PWA Install - Full event CRUD written back to Fastmail, PWA manifest + service worker, guided iOS install flow
Phase 4: Shared Lists + Live Sync - Named collaborative lists with item CRUD and real-time SSE co-edit sync
Phase 5: Web Push Notifications - VAPID push for event reminders, event changes, and list-change alerts

Phase Details

Phase 1: Foundation + Broker Spike

Goal: The app stack is running, both members can authenticate, and the CalDAV broker can read Fastmail calendars — with a confirmed go/no-go decision on personal-calendar cross-account sharing Mode: mvp Depends on: Nothing (first phase) Requirements: AUTH-01, AUTH-02, AUTH-03, CAL-01, CAL-08 Success Criteria (what must be TRUE):

Both members can reach the app URL, authenticate through Authelia OIDC, and land on the app home page without entering any Fastmail credentials
Sessions persist across browser restarts — neither member is asked to log in again on the next visit
Each member is assigned a stable, distinct display color that does not change between sessions
The broker successfully fetches and caches at least one event from the shared Fastmail calendar via CalDAV PROPFIND/REPORT
The personal-calendar ACL spike produces a documented go/no-go decision: either the broker token sees the wife's personal calendar after Fastmail share+accept, or the fallback strategy (shared-family-only or per-member app password) is chosen and recorded Plans: TBD

Phase 2: Calendar Display

Goal: Both members can see a unified, color-coded calendar aggregating all accessible Fastmail calendars across day, week, month, and agenda views — read-only, no write-back yet Mode: mvp Depends on: Phase 1 Requirements: CAL-02, CAL-03, CAL-07 Success Criteria (what must be TRUE):

Opening the app shows a color-coded calendar where each member's events appear in their assigned color, with shared events distinguishable from personal events
The user can switch between day, week, month, and agenda views and all events render correctly in each view
A recurring event (e.g., weekly meeting) displays all its occurrences correctly in the current view window, including correct behavior across DST boundaries
All-day events (birthdays, holidays) appear as full-day banners on the correct date with no timezone shift Plans: TBD UI hint: yes

Phase 3: Event Write-Back + PWA Install

Goal: Both members can create, edit, and delete events that are written back to the correct Fastmail calendar, and the app is installable to the iPhone and Android home screens with a guided onboarding flow Mode: mvp Depends on: Phase 2 Requirements: CAL-04, CAL-05, CAL-06, CAL-07, PWA-01, PWA-02 Success Criteria (what must be TRUE):

A member can create a timed or all-day event (including recurring events) in the app and see it appear in the native Fastmail app within the next sync cycle
A member can edit an existing event's title, time, or description and the change persists correctly in Fastmail
A member can delete an event and it disappears from all views on the next sync
On Android, the app shows a browser install prompt and installs to the home screen; on iOS, the app shows a guided "Add to Home Screen" walkthrough with annotated screenshots that a non-technical user can follow independently
The installed PWA opens full-screen without browser chrome on both iOS and Android Plans: TBD UI hint: yes

Phase 4: Shared Lists + Live Sync

Goal: Both members can create and manage shared named lists with real-time co-edit sync — edits by one member appear for the other without any manual refresh Mode: mvp Depends on: Phase 1 Requirements: LIST-01, LIST-02, LIST-03, LIST-04 Success Criteria (what must be TRUE):

Either member can create a named list (e.g., "Groceries") and delete a list they no longer need
Either member can add items to a list, check items off, reorder them by drag-and-drop, and delete individual items
When one member adds or checks off an item, the other member sees the change appear in the list within a few seconds without refreshing — even if they reconnect after a brief network gap Plans: TBD UI hint: yes

Phase 5: Web Push Notifications

Goal: Both members receive timely Web Push alerts for upcoming events, event changes made by the other member, and list changes — reliably on both iOS and Android Mode: mvp Depends on: Phase 3, Phase 4 Requirements: NOTIF-01, NOTIF-02, NOTIF-03 Success Criteria (what must be TRUE):

A member receives a push notification on their phone approximately 15 minutes before a calendar event starts — delivered to the installed PWA, including on iOS
When the other member adds or changes a calendar event, the first member receives a push notification with the event title and action described in the payload
When the other member modifies a shared list (adds, checks off, or deletes an item), the first member receives a push notification identifying the list and the change
After an extended period of app inactivity, push notifications are still delivered (subscription health-check prevents silent revocation on iOS) Plans: TBD

Progress

Execution Order: Phases execute in numeric order: 1 → 2 → 3 → 4 → 5 Note: Phase 4 depends only on Phase 1 and can begin as soon as Phase 1 is complete. It is serialized here to reduce work-in-progress.

Phase	Plans Complete	Status	Completed
1. Foundation + Broker Spike	0/?	Not started	-
2. Calendar Display	0/?	Not started	-
3. Event Write-Back + PWA Install	0/?	Not started	-
4. Shared Lists + Live Sync	0/?	Not started	-
5. Web Push Notifications	0/?	Not started	-

6.9 KiB Raw Blame History Unescape Escape