EXPO STARTER
An Expo starter that already runs.
Clone it, run it on your phone, and start on the part that is yours. Sign-in, subscriptions, a database and three AI features are wired together on iOS and Android.
What is in the Expo starter
Every item below runs in the demo app on the first clone. Nothing is a TODO.
- Expo SDK 57, React Native 0.86, React 19.2
- Typed end to end, one convention per problem, and a single command that runs every check the project makes of itself.
- Sign-in that is finished, not sketched
- Supabase Auth with Google, Apple and email, and every screen that has to exist around it. Users sit in your own Supabase project from the first build.
- Payments wired before the first screen
- RevenueCat purchases and restore, a subscription screen, and paid access the server decides rather than the client.
- Three AI features already shipping
- Streaming chat with threads, image generation and a scanner, each independent, on Supabase Edge Functions with the Vercel AI SDK. Your provider key never leaves the server.
- Your Postgres, your rows
- Supabase Postgres with the initial migration written, row-level security on every record a user owns, and generated types so a wrong column fails at compile time.
- One seed colour, a whole theme
- Uniwind brings Tailwind CSS v4 to React Native, compiled by Metro. Light and dark are generated from a seed.
- Instructions written for your coding agent
- Skills ship with the clone and describe the code in that release, so your agent reads where things go before it writes a line.
- A route to both stores
- EAS build profiles, screenshots generated from a Maestro flow, and release checklists that say what to prepare.
From clone to your phone
You need free Supabase and Expo accounts and an API key for your AI provider. The setup skill handles configuration, migrations, secrets and the first build, and asks you when it needs a sign-in or a key.
From there, your coding agent builds your idea on top. The skills that ship with the clone tell it where things go, so it extends the starter instead of rewriting it.
The starter, running on a device
Taken from the demo app you get on the first clone.
Onboarding, before the first screen of yours
A paywall the server decides
AI features you can keep or remove
To the App Store and Google Play
EAS build profiles are set up, store screenshots are generated from a Maestro flow, and there is a first-release checklist and an every-release checklist that say what to prepare.
Store accounts and review stay yours. You need an Apple Developer account and a Google Play developer account, and the included guides cover each step.
Expo starters compared
| A blank Expo project | NativeExpress |
|---|---|
| Expo Router and TypeScript | Expo Router and TypeScript, with one convention per problem |
| No sign-in | Google, Apple and email, with every surrounding screen |
| No payments | RevenueCat subscriptions, restore and a paywall |
| No database | Supabase Postgres with row-level security written |
| No AI | Chat, image generation and a scanner |
| Your agent starts from nothing | Agent skills that describe this exact code |
Guides
Start from a running app.
One payment, the full source on GitHub, and every future version at no extra cost.