Admit One

Admit One started with a Google Sheet as its database, read live via the Google Visualization API to avoid running a server. That worked until the dataset and the feature list both outgrew it: no real schema, no real auth beyond a shared passphrase, and no good way to enforce data integrity as more shows, venues, and photos piled in. The Sheet has since been retired for Postgres on Supabase, with the browser talking to it directly through Supabase's client SDK, row-level security scoping every read and write to the signed-in user, and real sign-in (Google OAuth or a magic link) replacing the old passphrase-protected write flow.

The point isn't logging tickets, it's looking back. Shows-per-year and monthly-heatmap views surface patterns I'd never have noticed manually (which months I actually go out, which years were dry spells), and the venue-size breakdown turns "dive bar to stadium" into an actual chart instead of a vague memory.

Setlist.fm, Last.fm, Deezer, and Google Photos all get proxied server-side instead of called directly from the browser, keeping API keys off the client and sidestepping CORS restrictions none of those services support.

The service worker never force-activates a new version, instead it surfaces an "Encore Available" prompt so I choose when to update, without losing my place mid-scroll.

No framework, no build step on the frontend, plain HTML/CSS/JS shipped as an installable PWA with a hand-written service worker, backed by Vercel serverless functions talking to Supabase Postgres. It's deployed on Vercel with a small CI workflow that bumps the service-worker cache hash on every push, and it's under active, ongoing development.