The problem
Consumer social products fail on trust: people will not upload years of pet memories to something that might lose them. That makes correctness and observability a product requirement, not an engineering preference.
Approach
- Treat the test suite as a launch gate rather than an afterthought.
- Wire real error monitoring before launch, not after the first incident.
- Verify claims against the deployed site rather than the local build.
Architecture
- Supabase Postgres with row-level security on all user content.
- Stripe for subscription billing; Capacitor for iOS and Android from one codebase.
- Sentry on both browser and edge, plus real-user web-vitals collection.
What shipped
- Memory book, milestones, and local playdate discovery.
- Native mobile builds and subscription billing.
- Error monitoring that surfaced and fixed a logger defect collapsing 25 distinct error sites into a single issue.
By the numbers
- Test files
- 164
- Tests
- 4,385
- CI workflows
- 22
Stack
React 19TypeScriptSupabaseStripeCapacitor
Building something like this?
Tell us what you're working on and we'll tell you honestly whether we're the right team for it.
Start a conversation