Skip to evidence →
tanyasingh
← Back to evidence index
Exhibit D · Open

Evidence folder

Weekly Tracker

Client
Personal project
Role
Creator & Lead Developer
Timeline
2026 · ongoing side build
PWAInstallable & offlineCustom service worker caches the full app shell — works with no network once installed.
0-configNo signup requiredRuns entirely on localStorage by default; Postgres sync is opt-in, not required.

Objective

Ship a free, install-anywhere weekly planner with a cozy Studio Ghibli-inspired look — a visual time-grid, offline-first PWA shell, and optional real-time shareable calendars — with zero required signup or setup.

Decision log

Choices under review — why they stuck, and what they cost.

  1. Decision 01

    Local-first by default, Postgres only when opted in

    WhyMost visitors just want a planner that works instantly — no account, no config, no server dependency to get value.

    TradeoffCross-device and shareable calendars only unlock once a database URL is configured — a deliberate progressive-enhancement boundary instead of a hard requirement.

  2. Decision 02

    Custom service worker + Web App Manifest over a PWA framework

    WhyA weekly planner only earns a home-screen icon if it's genuinely usable offline, not just cached shell markup.

    TradeoffHand-rolled cache and update logic instead of an abstraction — more control over install/update UX, more edge cases to own directly.

  3. Decision 03

    Server-Sent Events for shareable calendar sync

    WhyOptional passcode-protected shared calendars needed live, one-way sync across devices without the ops overhead of a websocket layer.

    TradeoffSSE trades bidirectional flexibility for a simpler, cheaper-to-run sync path that fits a side project's infra budget.

What we built

  • 7-day hourly schedule grid (7 AM–12 AM) with click-to-add tasks and automatic overlap layout
  • Configurable reminders — in-app toasts, native browser notifications, and sound alerts
  • Installable offline PWA via a custom service worker and Web App Manifest
  • Optional shareable, passcode-protected calendars with real-time cross-device sync

Filed stack · Next.js 16 · React 19 · TypeScript · Tailwind CSS v4 · Neon Postgres · Vitest

Panel observations · people

  • Obs. A

    Designed, built, and shipped the product end to end — UI craft, reminder engine, and optional sync/database layer

  • Obs. B

    Paired with a collaborator on real-time calendar sync and per-calendar notification scoping

  • Obs. C

    Held the codebase to a day-job bar: a Vitest suite, ESLint, and a documented README/AGENTS.md for future contributors

Discuss this kind of engagement → Contact