Back to Index
Vol. 01 Tech Jargon № 13
Tech Jargon · Project № 13

Shared Calendar

Two phones, two ecosystems, one source of truth. The day Mariah and I stopped double-booking each other.

The Analogy

The fridge-door calendar, upgraded.

Every couple ends up with the same artifact. A paper calendar on the fridge. Hand-written, half-legible, the one surface where both lives are visible. It works because it's shared by being in one place. Once you leave the kitchen, it stops existing.

This is that fridge, on our phones, that writes itself. Forward a flight confirmation. Drop a screenshot of a wedding invite. Tell it the dog has the vet at four. It files the event, tags whose calendar it lives on, and shows it in a weekly grid we both check.

One view we both check. No more "didn't see it on yours."
How It Works

Capture. Compose. Commit.

Input
It listens for events.
Forwarded emails, screenshots, parsed bookings, manual entries. Anything we send to the inbox lands here, with the original message kept on file.
→
Transform
It assigns who, when, where.
Categorizes by type (trip, dinner, dog, household), tags which of us owns it, normalizes the time zone, and ties the event back to the message that spawned it.
→
Output
It renders one weekly view.
A PWA that lives on both home screens. Mirrors finalized events into Google Calendar so push notifications and iCloud subscribers stay in sync.
Under the Hood

What's actually running.

Front Door Next.js PWA A web app you install to the home screen. No app store. Updates the moment we push.
Brain Inbox Parser Reads forwarded confirmations and screenshots, extracts the event, sorts by who and what.
Memory Supabase Postgres The canonical calendar and inbox. Both phones read from one source. No reconciling two truths.
Bridge Google Calendar Sync Pushes finalized events upstream. Apple Calendar subscribers, push notifications, and dog-walker invites stay current automatically.
Why it's built this way

Two-person calendar sharing collapses when each person lives in a different ecosystem. Apple won't render Google reliably. Google won't return the favor. Shared calendars are an afterthought in both. The fix is a third place we own, written into both phones, that each ecosystem already trusts through its native client.

Why It Matters

We stop double-booking each other.

Trips stop colliding with anniversaries. The inbox stops being the index of who's flying where. The dog stops getting two dinners.

The household runs on one calendar instead of two. The minute spent forwarding an email replaces the hour spent untangling a missed plan.