Agendula

A modern Material 3 Expressive task app for Android.
Keeps your tasks on your device, or on top of a tasks provider you already use. Open standards, no account required.

CI Android 10+ Kotlin + Compose Material 3 Expressive MIT License
Agendula is the task-list sibling to [Calendula](https://codeberg.org/jlmakiola/calendula). Where Calendula is a pure front-end over Android's `CalendarContract`, Agendula speaks the **dmfs `TaskContract`** — the same shape DAVx5 (and SmoothSync, DecSync, …) syncs your CalDAV `VTODO` tasks into. The name rhymes with its sibling on purpose: **Agendula** is *agenda* — Latin for “things to be done” — given Calendula's `-ula` ending. Calendula keeps your days; Agendula keeps your to-dos. (A Calendula flower head is botanically a cluster of many small *florets* — so the two apps are florets of one bloom.) ## Where your tasks live — your choice | | Where | Sync | Needs | |---|---|---|---| | **On your device** *(default)* | Agendula's own task store, bundled in the app | none yet — sync of our own is planned | nothing. No account, no permissions, no other app | | **In a provider you already use** | OpenTasks or tasks.org | whatever syncs it for you — DAVx5 and friends | that app installed, and its read/write permission | Agendula carries its own copy of the Apache-2.0 dmfs task provider, under its own name — so it **coexists with OpenTasks rather than replacing it**, and installing one never breaks the other. It is a fork of a proven schema, not a database written from scratch, which is why every CalDAV engine already understands it. Your tasks are exportable as standard iCalendar `.ics` files at any time, because data you can't take with you isn't really yours. > **Status: backend complete, UI catching up.** Storage, provider, reads and > writes, smart-list filtering, a self-scheduled reminder engine, and export are > built and unit-tested. The Material 3 Expressive screens are being built on > top, one at a time — the storage-mode picker and export screen are not there > yet. See [`docs/ROADMAP.md`](docs/ROADMAP.md) for status, > [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for how it's built, and > [`docs/STORAGE-AND-SYNC.md`](docs/STORAGE-AND-SYNC.md) for why storage works > the way it does. ## Sync sources (by design) In provider mode Agendula works with anything that writes to that provider — **DAVx5** (CalDAV), **SmoothSync**, **CalDAV-Sync**, **DecSync CC**, or any Android sync adapter — because it builds on the provider, not on any one sync app. Google Tasks / Microsoft To Do are out of scope by design (proprietary; they would mean owning a sync stack). Open standards — CalDAV / iCalendar / DecSync — are the lane. ## Translations Agendula ships in English so far, and would like not to. Translations are managed on a self-hosted **Weblate**, and partial ones are fine — an untranslated string simply falls back to English. **→ [Help translate Agendula](https://weblate.dev.jeanlucmakiola.de/engage/agendula/)** No coding needed: register on the Weblate server, pick (or request) a language, and translate the strings in your browser. You can also reach this link in the app from the top of **Settings → App language**. ## License MIT — see [LICENSE](LICENSE).