Problem
Managing a working day usually means four applications that do not talk to each other: a task list, a calendar, somewhere to write, and a document that describes the routine that is supposed to tie them together. Each has its own login, and none of them knows what the others already know, so the day starts with reconciling them by hand.
Our role
Design and implementation, from the data model through to the interface.
Approach
One application holds tasks and projects, a calendar, notes, and the daily review that closes the loop. Supabase provides the data layer and authentication; background work — the parts that should not happen while somebody is waiting for a screen — runs in Cloudflare Workers rather than in the client.
The interface is built around a small number of routines: capture, plan, work, review. Focus tools exist to keep one task in front of the user at a time, and notifications are treated as a thing to be earned rather than a default. A composed AI assistant is part of the design work, not something the application claims to do today.
Outcome
The core workspace — tasks, projects, calendar, notes, review — is built. Some supporting functionality, including a backup path, is not deployed, so it is listed as roadmap and kept out of the description of what works.
Notes
No personal task lists, calendar entries, or account details are published. The roadmap items are labelled as such wherever they appear.