Expo + Supabase App Builder

An opinionated path for shipping a small app on Expo + Supabase + EAS — written after taking one through both app stores. Its job is to get the order right and catch the failures that only show up on a cloud builder, a reviewer's device, or another OS.

The stack

What it covers

• Scaffolding order that avoids the most expensive rework (native modules listed and installed before the first build)
• Supabase schema, RLS policy design, and testing policies at the SQL level — including asserting negatives (what a stranger can't see, what a member can't change)
• Query client / mutation / store setup, tested against the live project before any screen calls it
• Image and file uploads (a different path than the web docs show)
• Universal links and web-deploy-before-store-build sequencing (iOS fetches link association files at install time)
• Store assets and copy, generated by script from a single logo
• Troubleshooting EAS build, submission, and Metro bundle failures that don't explain themselves

When to use it

Starting a new Expo + Supabase project, or partway through one and stuck on RLS design, auth wiring, native modules, universal links, or a store submission. Assumes this stack rather than helping you choose one.