One command builds an Expo app on React Native from the modules you pick and deletes the rest. What’s left reads like your own code.
An Expo and React Native app for iOS and Android, on your customers’ existing accounts, selling your plan in-app next to the Stripe you run.
One-time payment, from $49 · every app you ship
One-time payment, from $69 · every app you ship
Your app. Only the modules you picked.
Week two, skipped
01 · Native
02 · Store
03 · Code
The setup · Starter + Pro
One command builds the app from the modules you pick.
Pick one provider per row. Every option is a real, tested integration; the rest is deleted.
bun run setup
Tap any module below to add it, then open the terminal.
Styling
5 UI stacks
Theme tokens and dark mode from one file.
UI
Release
1 command to both stores
Cloud builds and auto-submit through EAS build and submit profiles.
Updates
Ship a fix without a store release
Over-the-air updates with a built-in “Update ready” banner.
Setup
No Mac required*
EAS builds iOS and Android in the cloud and submits to both stores from any OS.
Doctor
A checklist that goes green
Every missing key with a link to the dashboard that issues it.
Navigation
Screens are files
The native tab bar, large-title headers, modals, typed routes, React Compiler on.
The app layer
Data, state, storage, forms, translations - chosen once.
Imported from one place, no adapter layer left behind.
Data
State
Storage
Forms
i18n
Examples · Pro
2 finished example apps
Field Notes (journal) and Snap Recipe (AI vision), built on a fresh setup.
Built in
The boring parts, done.
Deep links, review prompt, error boundary, icons + splash, docs + llms.txt. Onboarding is one setup question.
Native
Widgets, Live Activities, native sheets and toasts.
An iOS home-screen widget and a Lock Screen / Dynamic Island Live Activity written in TypeScript, the Liquid Glass tab bar, SwiftUI sheets, system toasts, 120 Hz presses, keyboard-aware forms and six languages with Arabic right-to-left. The first run is a weather app that uses all of it.
Widgets
Push
Location
Continuous Native Generation
No ios/ or android/ folders.
Native projects are generated from one config file on every build, so an Expo SDK upgrade is a version bump, modules add and remove their own targets and entitlements, and fixes ship over the air while the binary stays put.
AI agents
Works with your AI agent.
AGENTS.md, an architecture graph, 3 Expo skills and a ReadyNative skill ship in the repo, so any coding agent starts from the conventions instead of guessing.
ReadyNativeworks withClaude CodeCursorCodexGitHub Copilot
Sign-in and payments · Pro
Accounts and subscriptions, screens included.
Pick one account provider and one billing provider. Stripe Checkout runs in Expo Go; RevenueCat and Adapty need a dev build.
Auth
Payments
App shell
Intro, consent, backend and tests, each optional.
Three slides on first launch, a GDPR and CCPA consent sheet, API routes in the same repo, and Jest with Testing Library. Each module ships its own tests, and they go when the module does.
Onboarding
Privacy consent
Backend
Testing
* RevenueCat, Adapty, push, widgets, MMKV and Unistyles need a dev build; everything else runs in Expo Go. Expo Go or a dev build?
Starter and Pro open on a weather app that puts every native module to work. Pro adds two standalone apps, each on a fresh setup with its own lockfile. All three boot with no .env at all: anything that needs a key says so on that screen.
The first-run demo: your forecast, on the Home Screen too.
A private, local-first journal that syncs once you sign in.
Photograph your fridge; get recipes for what is already in it.
Why an app
The browser is where people find you. The app is where they come back and pay.
Push notifications
Tell a customer their export is ready, their trial ends Friday, a teammate mentioned them. The push module registers the device token and ships a test script; your server sends through Expo’s push service.
A place on the home screen
An icon on the phone is one tap from your product; a tab in a mobile browser is not. Over-the-air updates keep that app current between store releases.
App Store and Google Play discovery
People search the stores for tools like yours. A listing is one more place to be found, with ratings next to it, and the in-app review prompt asks at a moment you choose.
In-app purchase
Apple’s purchase sheet with Face ID is the shortest path from free to paid on an iPhone. RevenueCat or Adapty wrap StoreKit and Play Billing, with the paywall and entitlements already wired.
Figures are from Sensor Tower’s State of Mobile 2026, linked above.
Your web stack carries over
Here is what you probably run on the web today and what it becomes in the app. Pick the same providers during setup and the app talks to the services your web app already uses.
On the web
Supabase or Clerk
In the app
The same user accounts as your web app
Put the project URL and anon key of your Supabase project, or the publishable key of your Clerk instance, in .env. Same project, same users: customers sign in with the accounts they already have. Sessions, protected routes, sign-out and the sign-in screens are wired.
Add sign-inOn the web
Better Auth
In the app
The same user table, served from the app’s API routes
The Better Auth option runs its server in the repo’s API routes. It ships with an in-memory database for development; point its adapter at the Postgres your web app’s Better Auth already uses and sign-in reads the same users.
The Better Auth moduleOn the web
Stripe
In the app
Web checkout next to in-app purchase, one “pro” entitlement
The web checkout guide runs Stripe Checkout and RevenueCat side by side. The Stripe route stores the signed-in user’s id on the subscription, RevenueCat logs in with the same id, and the app merges both into one “pro” check. It uses your Stripe account and a price you already have. Subscriptions your web app sold earlier don’t carry that id, so point the entitlements lookup at the way your web app records its customers.
Add web checkout next to the App StoreOn the web
PostHog or Amplitude, Sentry
In the app
Events and crashes under the signed-in user
Use the same PostHog or Amplitude project and the same Sentry organisation. The app identifies the signed-in user by the id your auth provider issues, so if your web app identifies by that id too, a customer’s web and app events land on one person.
On the web
Your API
In the app
Screens that call the API you already have
Pick TanStack Query, Apollo or SWR and point it at the REST or GraphQL API your web app already uses. Your backend doesn’t change. Want server code next to the app, such as the Stripe webhook? API routes ship it from the same repo, deployed to EAS Hosting or your own host.
Each option is a module with a public docs page listing every file, dependency and env key it adds. Setup picks one payments option; running Stripe and RevenueCat together is the web checkout guide above.
What this is not: a tool that turns your website into an app. ReadyNative is an Expo app with the plumbing done. You build your product’s screens on it, in React and TypeScript, against the API your web app already calls.
What you get
Pro ships a preset for this shape of app. One command applies it; any flag you add replaces that one pick, and whatever you don’t pick is deleted from the repo.
SaaS presetPro
bun run setup --preset saas
Supabase sign-in, RevenueCat subscriptions, Expo push, PostHog, Sentry and API routes, on NativeWind, TanStack Query and Zustand. Swap any of them for Clerk, Better Auth, Adapty, Stripe or Amplitude with one flag.
Snap RecipePro
The billing reference: three free scans, then Pro through two rails, in-app purchase and Stripe Checkout, unlocking one entitlement. Sign-in is Clerk; the Stripe checkout session, entitlements lookup and webhook are API routes.
Built with
Field Notes, the second example, is a local-first journal that syncs to Supabase on sign-in and gates Pro on a RevenueCat entitlement.
Read the examples guideA typical plan for one developer who knows React, not a guarantee. Your screens decide how long days two and three take, and App Review comes on top.
Day 1
Setup, with the keys you already have
Clone the repo, run setup with the SaaS preset or your own picks, and put the keys of your existing Supabase or Clerk project, PostHog project and Sentry organisation in .env. doctor lists whatever is still missing, with a link to the dashboard that issues it.
bun run setup --preset saasbun run doctor
Days 2–3
Your core screens, against your API
Pick the two or three things customers do most in your web app and build those screens. Screens are React components, navigation is files in a folder, and data comes from the API your web app already calls.
bunx expo start
Day 4
The paywall, on the products you have
Create the App Store and Play products in RevenueCat and map them to one “pro” entitlement. Selling on the web too? Add Stripe Checkout on your existing price with the web checkout guide.
Day 5
TestFlight and Play internal testing
Build on EAS and submit: iOS to TestFlight, Android to the Play internal testing track. After the one-time Play Console setup, every build goes up with one command.
bunx eas-cli build --profile production --platform all --auto-submit
Typical, not promised: a custom design system, native features of your own or a large API surface add days. App Review time is extra and is Apple’s and Google’s call; plan for one round of changes on a first submission. The Apple Developer and Google Play developer accounts are yours to open.
Questions
If your team writes React and TypeScript, yes. The app is Expo: screens are React components, navigation is files in a folder, styling can be Tailwind classes through NativeWind, and store builds run in Expo’s cloud, so nobody has to open Xcode. What is new is the platform - native navigation, touch targets, permissions, offline - and the docs and the two example apps cover those.
Read the QuickstartWithin specific rules. App Review guideline 3.1.1: digital subscriptions sold inside an iOS app go through in-app purchase, which is why the paywall is RevenueCat or Adapty. On the US App Store storefront the app may also link to your web checkout; elsewhere that needs Apple’s external purchase entitlement. Guideline 3.1.3(b) lets customers use a subscription they bought on your website, as long as it is also offered through in-app purchase in the app. Google Play has its own payments policy. The web checkout guide shows the storefront check that hides Stripe where it isn’t allowed. This is a summary of the guidelines, not legal advice: read them for your markets.
Add web checkout next to the App StoreYour purchase includes lifetime updates. Releases are tagged v<x.y.z>-sdk<major>, the changelog says what changed, and the “Update from upstream” guide walks through pulling a release into an app that already ran setup.
Update from upstreamNo. The app is a client of the API you already run: point the data layer at it and keep your server as it is. Share the auth provider - the same Supabase project, Clerk instance or Better Auth database - and customers sign in with the accounts they have. API routes are there for server code that belongs next to the app, such as the Stripe webhook; they don’t replace your backend.
A wrapper ships faster, and for some internal tools it is enough. The costs: web screens inside an app still feel like a website, App Review turns down apps that are mostly a repackaged site (guideline 4.2, minimum functionality), and push and in-app purchase need native code anyway. ReadyNative is the other trade: native screens you build in React, with push, in-app purchase and store releases already wired. It does not convert your site; you write the screens.
Pro gives one GitHub account access to the private repo and licenses up to 5 developers in one company, for unlimited apps, yours or your clients’. Clone it once and share the code with the licensed developers; after setup it is a normal Expo project in your own git history.
Start free with one fixed stack, or pay once for the picker and the paid-app modules. No subscription, unlimited apps, yours or your clients’, and lifetime updates on the paid tiers. Paid tiers are a private GitHub repo; bun, npm, pnpm and yarn all work.
The app, one stack, on GitHub.
$0MIT, forever
Trying Expo, or you already know you want this exact stack.
Clone on GitHubPublic repo. No account, no email.
What you get
The app, without accounts or payments.
Launch price, then $49first 20 buyers
$19one-time
Code STARTER20 is applied at checkout
Side projects, internal tools, apps with no login.
Get StarterConnect GitHub right after checkout. No subscription.
Everything in Free, plus
The app, with sign-in, subscriptions, push and analytics.
Launch price, then $69first 20 buyers
$49one-time
Code PRO20 is applied at checkout
Apps that sign users in and charge them.
Recommended
Get ProConnect GitHub right after checkout. No subscription.
Everything in Starter, plus
| Feature | Free | Starter | Pro |
|---|---|---|---|
| The app | |||
| Expo Router, typed routes, tabs, settings, dark mode, error boundary | Included | Included | Included |
| Runs in Expo Go on first launch | Included | Included | Included |
| Continuous Native Generation: no ios/ or android/ folders to maintain | Included | Included | Included |
| Weather demo on first run, removed by setup | Not included | Included | Included |
| Field Notes and Snap Recipe example apps | Not included | Not included | Included |
| Expo Push desktop app | Not included | Not included | Included |
| Stack | |||
| UI | NativeWind 4 | NativeWind 4 or 5 (RC), Tamagui, Unistyles, StyleSheet | Same 5 options |
| Data | TanStack Query | TanStack Query, Apollo or SWR | Same 3 options |
| State | Zustand | Zustand or Jotai | Same 2 options |
| Storage | SQLite key-value store | SQLite KV, MMKV or AsyncStorage | Same 3 options |
| Forms: React Hook Form with zod | Not included | Included | Included |
| i18n: i18next or Lingui, six languages, right-to-left Arabic | Not included | Included | Included |
| Onboarding flow | Not included | Included | Included |
| Tests: Jest + Testing Library, Maestro E2E flows | Not included | Included | Included |
| Native | |||
| iOS home-screen widget and Live Activity (Lock Screen, Dynamic Island) | Not included | Included | Included |
| Liquid Glass tab bar, SwiftUI sheets, system toasts | Not included | Included | Included |
| Location and an offline cache | Not included | Included | Included |
| Over-the-air updates with an in-app banner, in-app review prompt | Not included | Included | Included |
| Universal / App Links, icon and splash generator | Not included | Included | Included |
| Accounts and money | |||
| Sign-in: Supabase, Clerk or Better Auth, with protected routes | Not included | Not included | Included |
| Subscriptions: RevenueCat or Adapty paywall and entitlements | Not included | Not included | Included |
| Stripe web checkout, API routes in the same repo | Not included | Not included | Included |
| Push notifications | Not included | Not included | Included |
| Analytics with user identity: PostHog or Amplitude | Not included | Not included | Included |
| Crash reporting: Sentry | Not included | Not included | Included |
| Privacy and store | |||
| Consent framework: regional GDPR sheet, CCPA do-not-sell toggle | Not included | Included | Included |
| Export-my-data and delete-my-data | Not included | Included | Included |
| doctor --store: review check with a guideline id and a fix per finding, Data safety draft | Not included | Not included | Included |
| Tooling | |||
| EAS build and submit profiles | Not included | Included | Included |
| doctor: every missing key, placeholder and toolchain, with a link to fix it | Not included | Included | Included |
| AGENTS.md, an architecture graph and agent skills | Not included | Included | Included |
| Store-review agent skill | Not included | Not included | Included |
| Licence | |||
| Licence | MIT | Commercial | Commercial |
| Developers | Anyone | 1 | Up to 5, one company |
| Unlimited apps, client work included | Included | Included | Included |
| Lifetime updates | Not included | Included | Included |
By buying you agree to the Terms and the Licence.
One-time paymentTermsLicenceNo refunds once you have access
Secure checkout by Polar · Card, Apple Pay, Google Pay · VAT invoice included
The privacy work an app store reviewer or a regulator asks about is already in the repo, and it switches itself to whatever modules you pick.
Consent-first SDK startupPro
Analytics and crash reporting start only after the user says yes; until then no request leaves the phone.
A regional GDPR sheet and a CCPA do-not-sell toggle
Users in the EU, UK and similar regions get the consent sheet; California gets an opt-out toggle in Settings.
A data export file
“Export my data” writes a JSON file of what the app stores about the user, with tokens and secrets stripped.
In-app account deletionPro
App Store guideline 5.1.1(v): deleting the account removes the user from every service you configured.
iOS privacy manifest and Play Data safety draftsPro
The manifest is built from your modules; doctor --store drafts the Play Console Data safety answers.
A privacy policy draft
gen:privacy writes a policy from the modules you actually picked, for you or your lawyer to finish.
Starter ships the consent framework, export and deletion of on-device data; the analytics, crash and sign-in SDKs they govern are Pro modules. A draft is not legal advice.
FAQ
Yes. ready-native-free is a public, MIT-licensed repo with one stack already chosen and nothing else: Expo SDK 57, Expo Router, NativeWind 4, TanStack Query and Zustand, with tabs, a settings screen and dark mode. It runs in Expo Go. What it does not have is everything around the app: the picker (setup, the other UI stacks, forms, i18n, onboarding, the consent sheet, tests), EAS and CI, doctor, deep links, the OTA update banner, the review prompt, the agent files and the graph, and every service module. Clone it from https://github.com/ReadyNative/ready-native-free.
Read access to a private GitHub repo: right after checkout you connect your GitHub account in Polar’s customer portal and GitHub emails you the invitation. Inside: an Expo SDK 57 app, the 17 module categories (Starter has every category except sign-in, payments, analytics, crash reporting, push and API routes), the setup and doctor scripts, EAS build and submit profiles, Maestro test flows and the docs - and on Pro, the two example apps. You run setup once, and what is left is a normal Expo project - no runtime layer, no framework of mine on top of Expo.
If you can write React, yes. Screens are components, navigation is files in a folder, and store builds run in Expo’s cloud so you never open Xcode. The Quickstart gets the app onto your phone before you write a screen. On Pro, Field Notes is a full app to read first. You need Bun and Node 22.18 installed; that is it.
Not to ship. EAS builds iOS and Android in the cloud and submits to both stores from Windows or Linux, and Expo Go runs your project on a real iPhone from a QR code. You only need a Mac for the iOS simulator or if you insist on building iOS locally.
An Apple Developer account ($99/year), a Google Play developer account ($25, once), and a free Expo account (EAS has a free tier). That is the whole list. Everything the modules integrate (Supabase, RevenueCat, PostHog, Sentry…) has a free tier too.
Mostly. Expo Go is the free app that runs your project from a QR code without a build. Six modules ship native code and need a dev build instead - RevenueCat, Adapty, push notifications, the home-screen widget, MMKV and Unistyles. A dev build is your own build of the app, made once on EAS or locally; after that it works like Expo Go. Setup tells you which one your selection needs.
Yes. Pick TanStack Query, Apollo or SWR and point it at the REST or GraphQL API your website already uses. Already on Supabase or Clerk? Same project, same users. No backend at all yet? API routes let you ship server code from the same repo.
Selling subscriptions or anything digital inside the app? Apple and Google require their own in-app purchase systems, so pick RevenueCat or Adapty - both wrap the two stores and handle receipts and entitlements. Stripe is for physical goods, services, or checkout that happens on the web.
If you know Tailwind, keep the default, NativeWind 4, and move on. NativeWind 5 is a release candidate on the Tailwind 4 toolchain, one flag away if you want it now. Tamagui if you want its compiler and component library, Unistyles if you want C++-fast themes (dev build), StyleSheet if you want zero style dependencies. Screens import from one place either way, so switching later is an afternoon, not a rewrite.
No. The minimal preset is Expo Router, one UI stack and a handful of helpers. Everything else is a question during setup, and every module you do not pick is deleted from the tree - package.json included. Each module’s docs page lists the dependencies it adds.
Because you already write React. Expo is one TypeScript codebase with native UI on both platforms and a build service so you never open Xcode; it is what the React Native team recommends for new apps. If your team is Swift or Dart, this is not for you.
Expo ships a new SDK a few times a year and each one moves things. Your purchase includes lifetime updates: releases are tagged v<x.y.z>-sdk<major>, the changelog says what changed, and the “Update from upstream” guide walks through pulling a new version into an app that already ran setup.
Yes. One license covers unlimited apps for you, your company or your clients, and you can sell those apps. What you cannot do is resell or republish the starter itself. Starter is for one developer; Pro gives one GitHub account repo access and licenses up to 5 developers in one company.
Yes, on purpose. The repo ships AGENTS.md with the conventions and commands, an architecture graph (docs/graph.json + ARCHITECTURE.md, regenerated by one script when you add a route or module), and three Expo skills plus a ReadyNative skill under .agents/skills for Claude Code, Cursor and Codex (Pro adds a store-review skill). Every docs page has a copy-as-markdown button and the whole site is available as llms.txt, so an agent reads the same docs you do.
Not automatically. Students, open-source maintainers and anyone for whom USD prices hurt: tell me through the support form.
Card, Apple Pay and Google Pay, and invoices with VAT through Polar, which is the merchant of record for every order. Company purchases are welcome - put the company name and VAT number in at checkout and the invoice comes back with them on it.
No refunds once you have access to the repo, except where the law requires otherwise. That is why the free version is public and every module has a docs page listing every file it ships: you can see exactly what you are buying before you buy it.
Refunds in the TermsFor as long as ReadyNative is maintained: every future release reaches you at no extra cost. Lifetime means the life of the product, not a promise to update it forever. If updates ever stop, the licence is perpetual, so you keep building and shipping with what you have.
Yes, two ways. ready-native-free is the base app, public on GitHub at https://github.com/ReadyNative/ready-native-free. And every module has a docs page listing every file it adds, its dependencies and its env keys.
Browse the module docsWho made this
Just a front-end dev from Kazakhstan: 3+ years in the job, 20+ apps shipped, and what they taught me brought down to one terminal command.
Clone, run setup, paste your keys, submit to both stores. The wiring is already done.
Give them the app on the sign-in and billing they already use. Start with setup, your keys and one screen.
Guides
Set up expo-notifications without ejecting: APNs key, FCM v1, the Expo push token, the push notification tool, a curl test, deep links and fixes.
What Expo Go cannot run (push, in-app purchases, MMKV, widgets), how a development build differs, and how to make one with expo-dev-client or EAS.
AsyncStorage, MMKV or expo-sqlite/kv-store in Expo: Expo Go support, sync vs async API, speed, encryption, and how to migrate between them.
Clerk, Supabase or Better Auth in Expo: which ships prebuilt native screens, Expo Go support, session storage, pricing and account deletion.