Documentation pass after the 2.0 milestone:
- docs/ARCHITECTURE.md — principles (provider as single source of truth,
observer-driven UI, JVM-first tests, no network), layer + reminder
mermaid diagrams, navigation (overlay/held-key, no nav lib), and the
provider lessons (recurring-write invariants, conflict snapshots)
- docs/README.md — map of what documentation lives where, incl. the
convention that superpowers/ plans are historical artifacts while
.planning/ stays current
- README.md — showcase layout (centered header, badges, screenshot
gallery from the fastlane assets, grouped features, install/build/
architecture/roadmap sections); renders on Gitea
- .planning/{PROJECT,REQUIREMENTS,STATE}.md unstaled: read-only-V1 talk
removed, V1/V2 checklists marked shipped, state points at v3 + the
Locations & People go/no-go
release.yaml gains a gitea-release job: on every tag push it extracts the
tag's CHANGELOG section and creates a Gitea release with it as the notes.
No APK assets — distribution stays with the F-Droid repo. Idempotent
(skips an existing release), gated on the test job only so notes appear
even when the F-Droid upload hiccups.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4.6 KiB
Calendula — Current State
Last updated: 2026-06-11
Status
Milestone: 2 (write support) complete — v2.0.0 shipped 2026-06-11.
Phase: between milestones. Next: v3.0 (power-user features) and the
go/no-go on the "Locations & People" idea backlog (ROADMAP.md). Docs
pass done (ARCHITECTURE.md, README overhaul, planning docs refreshed).
Progress
-
Design spec written and committed (
docs/superpowers/specs/2026-06-08-calendar-app-design.md) -
V1 design decisions resolved (App name "Calendula", icon, seed color)
-
Plan 01 written and executed — foundation lands (theme, icon, i18n, Hilt, DataStore, CI green)
-
Plan 02 written and executed — data layer + permission flow + debug screen
-
Month view (S1) — 6-week grid, event dots, today marker, swipe nav, three states (replaces debug screen)
-
Week view (S2) — time schedule with overlap-resolved lanes, all-day strip, swipe nav, three states
-
Day view (S3) — single-column slice reusing the week layout
-
View-switcher (M1) wired — cycles Month ↔ Week ↔ Day
-
Event-detail screen (S4) — full-screen, humanized recurrence
-
Filter sheet (M3) — per-calendar visibility, grouped by account, persisted, applied centrally in the repository
-
Settings (M4) — appearance (theme, dynamic colour, week start), language (per-app locales), about
-
[~] Jump-to-date (M2) — cut from scope; "Today" half shipped in v0.5, date-picker dropped
-
Full event read (v0.6) — reminders, status, availability, access level, attendee role + self-response, foreign timezone, and linkified description URLs in the detail view; new domain enums + mapper unit tests. (A dedicated URL field was cut — no
CalendarContractcolumn backs it.) -
v1.1 write foundation —
WRITE_CALENDAR(onboarding asks READ+WRITE, only READ gates; contextual upgrade for v1.0 installs), read-only-calendar detection (CALENDAR_ACCESS_LEVEL→canModifyContents, actions hidden for WebCal/birthday calendars), delete from the detail screen (recurring: "only this event" via cancelled exception / "all events in the series"), repository + mapper tests -
v1.2 create event — full-screen
EventEditScreen(title, all-day, M3 date/time pickers with duration-preserving start moves, writable-only calendar picker preselecting the last-used calendar, location, description), "+" FAB on all three views prefilled with the visible day,insertEventwith provider-correct all-day normalisation (UTC midnights, exclusive end), domain/mapper/repository tests -
v1.3 edit event (shipped 2026-06-11) —
EventEditScreenreused for edit (detail-screen Edit action,canModify-gated, contextual WRITE upgrade), dirty-checked partialupdateon the Events row (recurring: series DTSTART moves by the user's delta, DURATION instead of DTEND), reminder diff by minutes (kept rows keep their method), simple recurrence picker (FREQ/INTERVAL/UNTIL/COUNT; complex RRULEs preserved verbatim and shown humanized),EventFormField.Recurrenceincl. settings default, recurrence also available on create; domain/mapper/repository tests. Review round 1: weekly BYDAY day-toggles in the custom picker ("every week on Mon+Fri"). Review rounds 2–4: occurrence edit pulled forward from v2.0 and made three-way like delete ("this" = exception row viaCONTENT_EXCEPTION_URI, "this and following" = series split, "all" = series update); delete equally three-way (truncation via RRULE UNTIL); the edit-scope question moved to save time (Google model) — dirty recurring saves park inSaveUiState.AwaitingScope, a changed rule drops the "only this event" option -
v1.4 reminder notifications (shipped 2026-06-11) — exported
EVENT_REMINDERreceiver →CalendarAlerts(SCHEDULED & due) → dedicated channel, tap opens detail (singleTop deep link); best-effort FIRED marking; one-time onboarding step requestingPOST_NOTIFICATIONSwith duplicate-reminders warning; Settings mirror. Provider only firesMETHOD_ALERTrows (AOSP-verified), so email reminders never reach us -
v2.0 conflict dialog + store polish (shipped 2026-06-11 as v2.0.0) —
EditSnapshotcompare on save (overwrite/discard; deleted → close), quick-add cut, calendar-switch → v3 backlog; F-Droid/README copy refreshed, fastlane screenshots DE+EN captured on-device
Next
- Decide the "Locations & People" go/no-go (INTERNET permission question)
— see
ROADMAP.mdidea backlog - v3.0 scoping: widget, full-text search, tablet layouts, ICS import, calendar-move
- Monitor the F-Droid build/publish for the v1.4.0 / v2.0.0 tags