makiolaj
05fc6e437f
The platform's contract as constants, and everything that decides what an incoming intent *means* — parsed, validated and range-checked as pure Kotlin, so hostile input can be tested without a device. `IntentExtras` reads a map rather than a `Bundle`, because the platform's typed getters cannot tell "absent" from "wrong type" and that distinction **is** the validation. The range rule: clamp what the user is doing now, drop what would define a future ring — hour 25 clamped to 23 rings at an hour nobody chose, so it is dropped and the editor opens instead. A link we cannot read names nothing, rather than falling back to "all of them": a caller who mistypes one timer's id must not dismiss every expired timer the user left standing. A repeat list sent non-empty from which nothing survives leaves the alarm incomplete, because a repeating alarm silently becoming a one-shot is a missed alarm next week.
Clockula
A modern Material 3 Expressive clock app for Android.
Alarms, timers, stopwatch and world clock. Open standards, no account required.
Clockula is the clock sibling to Calendula
(calendar) and Agendula (tasks). The
name follows theirs: clock, given Calendula's -ula ending. A Calendula flower
head is botanically a cluster of many small florets, so the three apps are
florets of one bloom — and they share one, floret-kit.
🚧 Early development. The spec is locked; the app is being built. See
docs/ROADMAP.mdfor where it actually is.
The honest difference from its siblings
Calendula is a pure front-end over Android's CalendarContract. Agendula speaks
the dmfs TaskContract. Both put a good interface on a standard someone else
already maintains.
There is no open provider behind a clock. Alarms, timers and laps are
Clockula's own data, so Clockula is the first app in the family to own its
storage — by design, not as a fallback. What that commitment is replaced with is
the first section of docs/PLAN.md, and it comes down to three
things:
- Clockula speaks Android's standard alarm contract. It implements
android.provider.AlarmClockin full, so your assistant and your automation apps can set alarms and timers in it exactly as they would in any stock clock, and the system status bar and lock screen show its next alarm. - World clocks are IANA time zones, not a bespoke city list that goes stale.
- Your data exports to a documented, versioned JSON file whenever you want it, because data you can't take with you isn't really yours.
Alarms that actually ring
An alarm app is only worth having if you can trust it, so Clockula treats that as the feature rather than the plumbing. Alarms are scheduled as real alarm clocks — doze-exempt, visible to the system — and re-resolved against your current time zone whenever anything moves underneath them, so DST and travel don't silently shift them.
When something on your device would stop an alarm ringing, Clockula tells you which setting it is and takes you there, instead of failing quietly at 7am.
Documentation
Start with docs/: PLAN.md is the spec and the
reasoning, ROADMAP.md is the status,
ARCHITECTURE.md is how the code is put together, and
RELEASING.md is the release runbook.
Building
git clone --recurse-submodules https://codeberg.org/jlmakiola/clockula.git
cd clockula
./gradlew assembleDebug
floret-kit is a submodule built from source as a Gradle composite build, so
--recurse-submodules is not optional. The included build needs to find the
Android SDK on its own: either export ANDROID_HOME, or drop a sdk.dir=… line
in a (gitignored) floret-kit/local.properties.
Licence
MIT — see LICENSE.