Personal time management where the day is a living plan, not a static calendar or a to-do list.
Plan it, live it, and see what actually happened next to what you planned.

Features · Screenshots · Getting started · Platforms

_{A fictional Tuesday: the plan on the left, what really happened on the right, wasted time striped in red.}

Features

🗓️ Plan in one click	Each weekday has its own template. Start the day as it is, plan it step by step, or start late from now.
⏱️ Track what is real	Now and Next, start, stop, pause, switch, and "also doing" for two things at once. Every second lands on the real timeline.
⚖️ Plan × reality	The plan stays frozen as a baseline. Compare it with the real timeline, replan the rest of the day, then close it.
✅ Tasks that fit blocks	Inbox, backlog, today and done, with keyboard shortcuts. Drag a task onto a block, or let it carry to the next day.
📊 Insights, no scores	Where the time went, wasted time and when it happens, planned × real per area, and changes against the previous period.
😴 Sleep and check-ins	Sleep from Health Connect or by hand, and a 20-second daily check-in about how honest the record is.
📅 Calendars	Google, Microsoft or any ICS link: events become blocks, and conflicts are flagged.
📴 Local-first	Everything lives in IndexedDB and works offline, then syncs to Postgres. The newest write wins.

Screenshots

Insights · what the real timeline says	Tasks · keyboard-first board

Light theme

_{Every screenshot comes from a throwaway browser with fictional data and no server behind it.}

Platforms

Folder	What	Status
web/	The app: Next.js 16 PWA, local-first (IndexedDB with Dexie) with sync to Neon Postgres	In daily use
desktop/	Electron companion: Now and Next floating in a corner, plus a tray / menu-bar icon	In use
mobile/	Android (Expo): a native shell around the web app, plus home-screen widgets, a lock-screen notification and OTA updates	In daily use
wear/	Wear OS (Kotlin): complications for Now, Next and start/stop that plug into any watch face	In use
design/	Design system, tokens, icon and visual reference
review/	Living planning doc: stages, flows, wireframes and validation

Every feature lives in the web app; the native apps only add what a browser cannot do (widgets, lock-screen notification, watch complications, a floating window). They talk to /api/sync and /api/snapshot with a device token, paired from the web by QR code or an 8-character code. The product and functional spec is in daily-os-product-functional-spec.md.

Getting started

cd web
cp .env.example .env.local   # DATABASE_URL, ACCESS_CODE_HASH, SESSION_SECRET at least
npm install
npm run dev

Command	What it does
npm test	Unit tests (Vitest)
npm run hash-code -- "<code>"	Hash for a new access code
npm run typecheck	TypeScript

• Database: create a Neon project and run web/db/schema.sql.
• Sign-in: there are no accounts. Each device signs in once with the access code and gets a signed session; other devices are paired from Settings › Device.
• Deploy: Vercel with the root directory set to web.

Desktop companion

cd desktop
npm install
npm run dev        # points at http://localhost:3000
npm run dist:win   # Windows installer

Stack

Layer	Technology
Web	Next.js 16 (App Router), React 19, TypeScript, Dexie, Lucide
Data	IndexedDB on each device, Neon Postgres as the sync hub
Android	Expo (WebView shell), react-native-android-widget, EAS Update, Health Connect
Watch	Kotlin, Wear OS complications
Desktop	Electron
Tests	Vitest

License

MIT

_{Built by Matheus Ervilha to find out where his days really go.}