Web Apps
DueReminder
A responsive PWA for reminders with two-way Google Calendar sync, recurrence, natural-language quick-add and offline support.

- Role
- Solo designer and developer
- Timeframe
- Sep 2026 - Nov 2026
- 38Commits
- ~9,300Source lines
- 117Tracked files
- 149Vitest cases
- 40Playwright cases
- 3D1 migrations
Problem
Reminder apps tend to get recurrence, time zones and offline edits wrong, and calendar sync can silently overwrite or lose changes. I wanted one where those cases are handled and tested.
Approach
- Run the API on Hono and Cloudflare Workers with D1, and a React 19 and Vite PWA that caches reminders in IndexedDB.
- Store recurrence as RRULE and sign in with Google OAuth with PKCE in two steps, asking for the Calendar scope only when sync is turned on.
- Cover the risky paths (recurrence, sync, offline replay, sessions) with unit and e2e tests.
Result
A tested app with 149 Vitest and 40 Playwright cases. It is not deployed yet, and live Google sync has not been tested end to end.
Problem
DueReminder is a reminder app with quick-add, recurring reminders and optional two-way Google Calendar sync. The hard parts are correctness ones: recurrence across daylight saving changes, edits made offline, and sync that must not lose or overwrite data. It is a solo project, design and code are mine.
Approach and decisions
The server is Hono on Cloudflare Workers (server/src/worker.ts) with D1 and 3 migrations. A cron trigger runs every minute through a scheduled handler (server/src/scheduled.ts), kept out of the Worker entry. The client is React 19 with Vite as an installable PWA, with an IndexedDB cache for offline use. Recurrence is stored as RRULE.
Sign-in uses Google OAuth with PKCE in two steps: the sign-in scope first, and the Calendar scope requested separately. Sessions use a __Host-rs_session cookie, with CSRF helpers and a per-isolate in-memory rate limiter. The app began on Fastify and SQLite and was ported to Workers and D1 (d23214b, 8450bd6). Server-sent events were replaced by a refetch on focus and every 60 seconds (13155a9, recorded in DECISIONS.md).
What broke and how it was fixed
- Overdue recurring series. They now advance past the current time, keep wall-clock time across DST gaps, and restrict FREQ (997809c).
- Failed sync pushes. They stay visible instead of vanishing, and remote text is clamped (d778945).
- Offline replay. Queued edits rebase PATCH versions and are never dropped on a 401 or 5xx response (74617fe).
- Sessions. A strong SESSION_SECRET is enforced, the id_token is verified, and the session is rotated on login (9f9411d).
Results
38 commits between 2026-09-20 and 2026-11-05 produced about 9,300 lines of source across 117 tracked files, with 149 Vitest cases and 40 Playwright cases in 24 test files. The repository is public.
Limits
The app is not deployed: the D1 database id in wrangler.jsonc is a placeholder. Live Google OAuth and Calendar sync have not been tested end to end. Google Tasks has no code. There are no users and no adoption claims.

