makiolaj
af9b2cb5c8
versionName 1.0.0, versionCode 10000. Merging this to main triggers .gitea/workflows/release.yaml, which builds it, publishes to the F-Droid repo, and mints the v1.0.0 tag — and this is the release where `prerelease` flips to false on its own, since the pipeline derives it from MAJOR. CHANGELOG's 1.0.0 section covers the own store, list management, recurrence, iCalendar export, the storage picker and the copy path, then the fixes to the external-provider mode that 0.4.0 and earlier used for everything — the reverting due times, the all-day drift, the silent save failure on tasks with a duration, recurrence detection on tasks.org, the inert reminder field, and the provider-failure recovery. Nothing about the dropped authority or the custom permissions: they never reached a release, so there is nothing for a user to have lost. `changelogs/10000.txt` is `scripts/sync_changelog_to_fastlane.sh` output, for the official F-Droid listing, at 471 of the 500 characters F-Droid will show — the section is written to that budget rather than trimmed to fit it, since the same text is the Gitea release notes. The detail behind each line is in the commit messages, CHANGELOG's older entries stay as they were. Still open before this merges, per docs/RELEASING.md step 4 and ROADMAP: `./gradlew :app:connectedDebugAndroidTest` against the tip, and `scripts/verify-release.sh` on a real device.
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.
Agendula is the task-list sibling to Calendula.
Where Calendula is a pure front-end over Android's CalendarContract, Agendula
keeps its own store, designed around RFC 5545's VTODO — the same tasks DAVx5
(and SmoothSync, DecSync, …) sync out of your CalDAV server. It can also read and
write a tasks provider you already have, for anyone already syncing that way.
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 database | none yet — CalDAV 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's own store is an ordinary app database — nothing is published to other apps, so there is no authority to clash over and no permission to grant. It coexists with OpenTasks rather than replacing it: installing one never breaks the other, and if you already sync through a provider, that keeps working exactly as it did.
Switching between the two moves nothing — each store keeps its own tasks — so Settings → Storage asks before it switches, and offers to copy a provider's tasks into Agendula's own store when you want to move over. The copy is taken once and the originals stay where they are; it is not an ongoing sync in either direction.
Recurring tasks are expanded per RFC 5545, and everything the schema does not model is round-tripped verbatim rather than dropped — so passing your tasks through Agendula does not quietly lose fields a server sent.
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, 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.mdfor status,docs/ARCHITECTURE.mdfor how it's built, anddocs/STORAGE-AND-SYNC.mdfor why storage works the way it does.
Sync sources (by design)
In external-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.
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.