Daffy's Mods
← All buildsApps & tools

TrackBoard

TrackBoard is a personal "life OS": tasks, projects, habits, school, practice, money and a journal in one web app, drawn in a hand-sketched notebook style. It is local-first: everything is stored in your browser and works offline, and it installs to a phone or desktop like an app (a PWA, a web app you can install). An optional Supabase backend adds sign-in, sync across devices, shared projects and push reminders.

  • Updated Oct 4, 2026
  • 3 pictures
  • 9 updates
TrackBoard, first picture

Status: works as a local app and was deployed on Vercel with Supabase sync; code last changed in May 2026, and the base Supabase schema is not in the repo yet · Visibility: public · Last updated: 2026-10-04

Contents

Screenshots

The board: today’s win, today’s schedule, practice streaks, school, finances and this week

The board, the first screen every day: one win for today, what is scheduled, practice timers with streaks, school, money this month and the week’s streak.

The Morning standup box: yesterday, today and blockers, saved to the journal

The morning standup: three quick lines that are saved to that day’s journal.

First run: a sketched card asking what to call you, with the timezone already picked

First run asks for a name and picks up your timezone, or you can skip setup.

Features

Requirements

Install

These steps come from package.json and the setup guides in supabase/. They have never been tested on a fresh PC.

Windows (PowerShell):

  1. Install Node.js 22 LTS from nodejs.org and Git from git-scm.com.
  2. Get the code:
    git clone https://github.com/DaffyDabz/trackboard.git
    cd trackboard
  3. Install packages (.npmrc sets legacy-peer-deps=true, so peer-version conflicts do not stop the install):
    npm install
  4. Start it and open http://localhost:5173:
    npm run dev

With no configuration the app runs fully on your device: the sign-in and sync screens stay hidden and everything is saved in the browser.

Optional: Supabase sync

  1. Create a project at supabase.com.
  2. Copy the example settings and fill in your project URL and publishable (anon) key from Project Settings > API. Never put the service_role key in this file.
    Copy-Item .env.example .env.local
    notepad .env.local
  3. Set up the database. The original tables (tasks, projects, skills, accounts and the rest) were created by hand in the Supabase dashboard and are not in the repo yet; the files in supabase/migrations/ only add to them. A fresh project needs that base schema first. Then run the migrations in date order in Studio > SQL Editor (see supabase/migrations/README.md).
  4. Under Authentication > URL Configuration > Redirect URLs, add http://localhost:5173/ and your deployed URL. For Google or Apple sign-in, follow supabase/OAUTH_SETUP.md.
  5. Restart npm run dev. The app now asks you to sign in and syncs.

Optional: push reminders

Follow supabase/PUSH_SETUP.md. In short:

  1. Make a VAPID key pair (the keys browsers use to trust your push messages): npx web-push generate-vapid-keys
  2. Put the public key in VITE_VAPID_PUBLIC_KEY (in .env.local and on your host).
  3. Give the Edge Functions their secrets and deploy them:
    supabase login
    supabase link --project-ref <your-project-ref>
    supabase secrets set VAPID_PUBLIC_KEY="<public-key>" VAPID_PRIVATE_KEY="<private-key>" VAPID_SUBJECT="mailto:you@example.com"
    supabase functions deploy send-notification --no-verify-jwt
    supabase functions deploy notify-due --no-verify-jwt
    --no-verify-jwt lets anyone who knows a function’s URL call it, so send-notification checks the caller itself: only the server’s own reminder job (the service-role key) or the signed-in owner of user_id can send. Paste the keys without the < > (the function also strips stray quotes and brackets).
  4. Run supabase/migrations/20260430_push_tables.sql (it creates the push_subscriptions and notifications_sent tables with row-level security), then schedule the pg_cron jobs that call notify-due every 5 minutes and clean up once a day, as described in supabase/README.md. Keep any key a cron job needs in Supabase Vault, never typed into SQL files.
  5. In the app: Settings > Notifications > Enable, then Test.

Habit and skill reminders at an exact time use a third function, reminder-dispatcher, scheduled every minute; its deploy and cron.schedule example are in the comment at the top of supabase/functions/reminder-dispatcher/index.ts. The calendar feed needs supabase functions deploy ical-feed --no-verify-jwt.

Run / Use

Command What it does
npm run dev Development server on http://localhost:5173 (the service worker is off here, so offline mode and push only work in a production build)
npm run build Type-check, then build the site into dist/
npm run preview Serve the built dist/ locally to try the real PWA

First steps:

  1. The onboarding wizard adds three starter skills; change their goals or remove them.
  2. Add tasks from the quick-add box (n), or press Ctrl+K to search and jump anywhere.
  3. Install it: in Chrome or Edge use Install app in the address bar; on an iPhone use Safari’s Share > Add to Home Screen.
  4. Back up: Settings has a full JSON export. Without sync, your data lives only in that browser, so clearing the site data deletes it.

Configuration

Environment variables (VITE_ ones are built into the site at build time, so rebuild or redeploy after a change):

Variable Where Used for
VITE_SUPABASE_URL .env.local and your host Supabase project URL; sync and sign-in
VITE_SUPABASE_ANON_KEY .env.local and your host Publishable (anon) key only; sync and sign-in
VITE_VAPID_PUBLIC_KEY .env.local and your host Push reminders (not in .env.example; add it yourself)
VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY, VAPID_SUBJECT supabase secrets set Edge Functions that send push
SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY Set by Supabase for Edge Functions Server-side database access
SUPABASE_PROJECT_ID Your shell Only for npm run supabase:typegen
ANALYZE=1 Your shell npm run build also writes dist/bundle-stats.html

Example .env.local (placeholders):

VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SUPABASE_ANON_KEY=your-publishable-anon-key
VITE_VAPID_PUBLIC_KEY=your-vapid-public-key

.env, .env.* (except .env.example) and .vercel/ are gitignored.

Settings saved inside the app (in the browser, not in files): the Anthropic API key and model (default claude-sonnet-4-5), the Canvas token, theme, notifications, shutdown-ritual time, swipe actions and auto-archive days.

How it works

Project layout

Path What lives there
src/pages/ One file per screen: Dashboard, Tasks, Projects, Calendar, Forecast, Habits, Skills, School, Finance, Journal, Goals, Whiteboard, Wrapped, Settings and more
src/components/ Shared parts: hand-drawn controls (ui/), charts, layout and navigation, sign-in, onboarding, focus timer, AI panels, modals
src/lib/ App logic: sync, realtime, push, AI, quick-add parser, recurring tasks, imports and exports, keyboard chords
src/lib/db/ Dexie database and schema, per-feature data helpers, Supabase row mappers, unit tests
src/lib/crypto/ On-device token encryption
src/sw.ts Service worker (precache, push, notification clicks)
public/ App icons
supabase/functions/ Edge Functions: send-notification, notify-due, reminder-dispatcher, ical-feed
supabase/migrations/ Dated SQL migrations, applied by hand
supabase/OAUTH_SETUP.md, supabase/PUSH_SETUP.md Google and Apple sign-in setup; push setup
vite.config.ts, tailwind.config.js, eslint.config.js, tsconfig*.json Build, style, lint and TypeScript settings

Development

npm run lint          # ESLint
npm test              # Vitest, once (jsdom; tests live next to the code as *.test.ts)
npm run test:watch    # Vitest in watch mode
npm run test:ui       # Vitest browser UI
npm run build         # tsc -b, then vite build
$env:ANALYZE = '1'; npm run build; Remove-Item Env:ANALYZE   # bundle treemap in dist/bundle-stats.html

npm run supabase:typegen regenerates src/lib/db/supabase-types.ts. The script uses $SUPABASE_PROJECT_ID (POSIX shell syntax), so on Windows run it from Git Bash or WSL, or run the supabase gen types command yourself.

Deploying the site (Vercel). Vercel detects Vite, runs npm run build and serves dist/. Set the VITE_ variables under Project > Settings > Environment Variables (Production, Preview and Development) and redeploy after any change, because they are baked in at build time. Either connect the GitHub repo in Vercel (pushes to the main branch deploy to production, other branches get preview URLs) or deploy from a linked folder with the Vercel CLI (npx vercel for a preview, npx vercel --prod for production). Add the deployed URL to Supabase’s redirect URLs, and to the Apple Services ID domains if you use Apple sign-in.

Database changes (Supabase migrations). Each change is a file named YYYYMMDD_short_name.sql in supabase/migrations/, written with if not exists so it is safe to run again. They are applied by hand: open Studio > SQL Editor, paste, run. The Supabase CLI migration runner is not used. Add a row to supabase/migrations/README.md, update the matching mapper in src/lib/db/mappers.ts (sync must keep working before the migration is applied), and regenerate the types.

Edge Functions deploy with supabase functions deploy <name> --no-verify-jwt. That flag makes each function a public URL with no sign-in check, so each function must check its caller itself; send-notification does.

Coming soon

Keep this list current: when an item ships, move it to Recent changes with the date, then add what is next.

Recent changes

Earlier milestones, dated by the database migrations (before the repo existed):

None. TrackBoard stands on its own.

Credits and license

Built with React, React Router, TypeScript, Vite, Tailwind CSS, Dexie.js, Zustand, date-fns, chrono-node, rough.js, Lucide, dnd kit, Papa Parse, react-markdown, vite-plugin-pwa and Workbox, web-push, Vitest and Testing Library. Services: Supabase (Postgres, Auth, Realtime, Storage, Edge Functions on Deno), Vercel hosting, and the optional Anthropic API. Each keeps its own license.

TrackBoard itself is an original project by DaffyDabz, released under the MIT License.

More builds

Apps & toolsGrimmicThe audiobook that reads itself, and a good e-reader too. Grimmic is a Windows desktop app for your ebooks (EPUB, PDF, TXT, Markdown) that works two ways.Updated Oct 4, 20263 picturesApps & toolsAuto ClickerA standalone Windows auto clicker in the style of OP Auto Clicker.New1 pictureApps & toolsGrimmic MobileThe phone and tablet version of Grimmic: an e-reader and an audiobook in one.New6 pictures