Overview
Daily Rhythm is a private planning workspace built around the difference between recurring behaviour and finite work. Habits answer “did I practise this today?”, routines break repeated sequences into steps, and tasks represent things that can actually be completed. Goals and milestones connect those daily actions to longer-term outcomes.
The application is available only to existing accounts. This public case study describes the implementation without exposing anyone’s schedules, reflections, calendar events, or personal progress.
One workspace, distinct concepts
The dashboard combines habits, to-dos, routines, goals, milestones, quick-capture inbox items, daily check-ins, journal entries, and weekly reviews. These records share a visual system but keep separate data models because they have different lifecycles.
- Habits store completion by day and retain history.
- Tasks support due dates, estimates, recurrence, notes, and completion state.
- Routines contain ordered steps with their own daily completion records.
- Goals contain draggable, ordered milestones and optional target dates.
- Inbox items capture thoughts quickly before they are processed into the right system.
- Check-ins record mood, energy, sleep, and a short note.
- Journal and weekly-review archives make previous reflection useful instead of disposable.
Interaction design
Goals and milestones can be rearranged directly. Mutations use explicit API routes and persist stable position values rather than relying on whatever order the browser happens to display. Destructive actions ask for confirmation, while the interface updates small actions without forcing a complete page reload.
The responsive layout treats each part as a focused tool rather than one continuous form. A collapsible sidebar keeps the application usable on phones without permanently consuming the screen.
Calendar integration
Google Calendar is optional and account-scoped. Daily Rhythm stores its own selected calendar independently from the Cookbook selection, so personal scheduling does not accidentally change where shared meal plans are written. OAuth tokens are encrypted at rest and never sent to the browser as raw credentials.
Ownership and deployment
Every query and mutation is scoped to the authenticated owner. Public registration is disabled, private pages are excluded from indexing, and the application runs as part of a Dockerized Next.js service on a home server behind a reverse proxy.
What I learned
Daily Rhythm became useful once each type of entry had a clear job. A habit keeps a history, a task can be finished, and an inbox item exists only until I decide where it belongs. Those boundaries matter more to me than the number of features on the dashboard.