Chapter
A serverless social reading app for iOS, Android and web. One engineer, one month, and the scope a small team would put on a half-year roadmap.
1engineer
3platforms
27languages translated
21decision records
// The constraint
Chapter had stalled: no infrastructure, no database design, no path to deploy, and no budget for a team. Getting it out meant choosing a stack that does a lot with very little, and being strict about the few parts that carry real risk.
// What shipped
Book clubsClosed clubs with a current book, a deadline and each member's progress on it.
Badge engineBadges are data. New ones ship from the backoffice without an app release.
Real-time feedActivity feed and notifications, live.
27 languages translatedEnglish, Portuguese and Spanish ship first; the other 24 are ready to publish as remote packs.
BackofficeA separate web app; every admin action goes through an audited function.
Remote configFeature flags, app version rules and banners, changed without a release.
// How it's built
- Serverless
- Expo
- React Native
- Supabase
- Postgres
- Edge Functions
- pgTAP
- Vite + React
- Sentry
- CI
- Serverless. Supabase manages Postgres, Auth, Realtime and the Edge Functions. There are no servers to run.
- One Expo codebase for iOS, Android and web.
- The app talks to Postgres directly through supabase-js and Realtime. Row Level Security is the security boundary: every table has it enabled and covered by pgTAP tests.
- Edge Functions sit to the side: book search and import from Open Library and Google Books, rate limited per user and cached, plus push notifications. Clients cannot write the catalog; only the service role does.
- The backoffice is a separate Vite + React app. Admins use their own session and audited database functions, never the service role.
- Remote config reaches the app through a single public function,
app_config(), with code defaults as the fallback. - Sentry with personal data stripped, plus our own anonymous telemetry instead of third-party tracking.
app_config(). RLS policies, not app code, decide who can read what. Only the Edge Functions write the catalog; the backoffice uses the admin's own session and audited functions.## Decision Use Supabase: Postgres + Row Level Security + Realtime + Auth + Edge Functions. The client uses `supabase-js` directly; RLS is the security boundary (the equivalent of Firestore rules); Realtime pushes changes without hand-written websockets. ## Consequences - Joins, aggregates, full-text/trigram search and triggers are plain SQL; schema lives in versioned migrations; TS types are generated from the schema. - Nothing is protected by hiding endpoints: **every table must have RLS enabled and tested** (`supabase/tests`). …
// How I worked
Every significant choice went into one of 21 decision records, every change was reviewed, and a QA pass on a real device fixed 35+ issues before beta. AI tools sped up the implementation; the decisions and the review stayed mine.
// Where it is
Heading into Android beta. The Play Store link goes here when it opens.