STARTER KIT
A React Native starter kit you can ship from.
Sign-in, subscriptions, a database and three AI features are already wired together and running on iOS and Android. You bring the idea.
What the starter kit contains
Not a scaffold with TODOs in it. Every item below runs in the demo app on the first clone.
- 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.
Screens that already exist
Taken from the demo app you get on the first clone, not from a mockup.

Sign-in, with every surrounding screen

The paywall, decided by the server

Streaming AI chat with threads
Why a starter kit rather than a fresh project
The hard parts of a mobile app are not the screens. They are the pieces that only fail in production: a sign-in flow that survives a cancelled Apple prompt, a paywall the server decides rather than the client, a receipt that restores on a new device, row-level security that holds when a user guesses an id.
Each of those is a known problem with a known answer, and each one is a week of your life the first time you meet it. A starter kit is worth having when it has met them already — and worth nothing when it has only stubbed them.
Against the free options
There are good free React Native starters. They solve a different problem, and for some projects they are the right answer.
| Free starters | NativeExpress |
|---|---|
| Navigation, linting and a theme | Navigation, linting and a theme, generated from one seed colour |
| Auth left to you, or email only | Google, Apple and email, with every surrounding screen |
| No payments | RevenueCat purchases, restore and a server-side gate |
| No AI | Chat, image generation and a scanner, each removable |
| No database opinion | Supabase Postgres, migration and RLS written |
| Community issues | Discord with the founders, and lifetime updates |
Start from a running app.
One payment, the full source on GitHub, and every future version at no extra cost.
