The alarm is part of the plan now
My Next: Todo 1.3.0 is live on the App Store.
This release adds a wake alarm, but the interesting part is not that a todo app can make a noise in the morning. It is that the alarm now sits beside the day it belongs to.
The alarm belongs to the day
You can set an alarm for tomorrow from My Todos, or give each weekday its own time in Weekly Routine. That makes the wake-up time part of the same plan as everything that follows it, rather than a separate setting in a separate app.
The alarm has built-in melodies, optional gradual volume, and snooze. It can also be haptic, subject to the phone's settings, or a silent day-start notification. A linked bedtime reminder works backwards from the wake time using the amount of sleep and wind-down time you choose. It does not monitor sleep stages or try to guess the perfect moment to wake you yet. Smart wake and sleep-stage work is next in line for My Next: Todo, alongside an Apple Watch app; both are future directions, not features in this release.
The most useful part may be what happens to Todo notifications overnight. When holding is enabled, eligible notifications wait from bedtime — or midnight when there is no bedtime reminder — until you stop the alarm. Snoozing keeps them held. A silent alarm releases them at its scheduled time.
All of those alarm options are included in the free version for up to three active alarm days. My Next: Extra removes the day limit; it does not hide the useful alarm settings behind the subscription. Alarms and routine alarms are included in backup and restore too.
The shorter version is now at What's New, and the details live in the Wake Alarm help article.
What's new in Build Studio
Build Studio can now compare how each role performs across projects. Every completed run adds a durable scorecard record per role and workflow step: findings, rounds, duration, token usage, cost, model, and CLI. There is deliberately no made-up composite score. The useful comparison is narrower — why does the same role converge in one project and take several rounds in another?
Building that exposed two measurement bugs. Codex agents had been reporting no token usage because the collector only knew how to follow Claude session IDs. And every model it did not recognize was silently priced as Sonnet. Codex usage is now read from its own rollout record, and an unknown price produces unpriced, not a confident-looking estimate. One historical reviewer had 508,160 cache-read tokens that the old accounting never saw.
The Build Studio changelog has the full upgrade note. Managed projects need no changes.
Elsewhere
DeskRhythm on Android moved through first-run onboarding, opt-in analytics, Play Billing and the Extra paywall, then added location-based Room switching. The location feature deliberately runs one check when the app comes to the foreground — no background location permission, no continuous tracking. Home office versus office is the intended case; when an approximate location could match more than one saved place, it refuses to guess.
Fazon found two problems by testing the live AI and coaching paths rather than their happy-path fixtures. The cloud photo classifier's main failure was a language boundary — Swedish food labels, not the model's ability to recognize the food — and the weekly coach was learning a new energy-expenditure estimate without ever applying it to the calorie target. The language fix has started landing. The target recalibration now has a gated design and pre-implementation tests; it is not shipped yet.
What's next
DeskRhythm for Android keeps moving forward. The foundations are in place; the work now is to keep closing the distance between a capable Android build and something ready to put in people's hands.
I am also looking into what useful watch apps could look like across My Next: Todo, List, and Note. The first question is not how to mirror the phone apps on a smaller screen, but which moments are genuinely better on the wrist. That is exploration, not a commitment or a shipped roadmap.