A React Native boilerplate built for AI
Cursor and Claude Code don't fail because they're bad at React Native. They fail because a blank Expo project gives them nothing to anchor to. This codebase fixes that with strict TypeScript, feature-first folders, an explicit rules system, and a memory system your AI reads before writing. So navigation works, state stays consistent, and the code matches the patterns already there.
Expo SDK 55, the New Architecture, RevenueCat, Supabase, Firebase, MMKV-backed offline-first sync, and the U-AMOS 2.0 memory system. Clean and shippable out of the box.
Built by Malik Chohra (9 years of mobile engineering), written for the way AI tools reason about code.
What's inside this React Native starter kit?
- React Native 0.83.6 with the New Architecture enabled
- Expo SDK 55.0.17 (latest stable)
- TypeScript in strict mode, fully typed end-to-end
- Authentication: Apple, Google, Email/Password, Forgot Password, biometric (Face ID, Touch ID)
- Monetization: RevenueCat with paywall, free trial, restore purchases, A/B variants
- Backend: Supabase (Auth + Postgres + Row-Level Security)
- Offline-first reference feature: MMKV cache, optimistic UI, sync queue, conflict resolution
- Firebase Analytics + Crashlytics + Remote Config + Cloud Messaging
- Sentry bundled for richer error context
- EAS Build (development / staging / production) + EAS Submit
- Testing: Jest + Testing Library (unit and integration)
- State: Redux Toolkit + RTK Query + Redux Persist (MMKV-backed)
- Navigation: typed React Navigation (Stack + Bottom Tabs + Drawer) with deep linking
- UI: @shopify/restyle design system with 60+ components
- Internationalization: English, French, Spanish (auto-detected, easily extensible)
- U-AMOS 2.0: 9-file memory bank, 10+ rule packs, 97+ AI articles, generators
How this compares to other React Native boilerplates
| Feature | AI Mobile Launcher | Ignite | create-expo-app |
|---|---|---|---|
| Built for AI tools (Cursor, Claude Code) | U-AMOS 2.0 memory bank + rules + generators | No | No |
| Monetization (RevenueCat) | Pre-wired with paywall + trial | Manual setup | No |
| Offline-first reference feature | MMKV + sync queue + conflict resolution | No | No |
| CI/CD (EAS Build profiles) | Included (dev / staging / prod) | Included | No |
| Expo SDK | 55.0.17 | Latest | Latest |
| Cloud + on-device AI providers | AI Pro tier → | No | No |
Want the long version? Read AI Mobile Launcher vs a normal React Native boilerplate and vs vibe-coding tools.
Get early access
Beta is open. Submit your details to get access to the private repository.
Request Beta Access
All three fields are required. We'll add you to the private GitHub repo.
Frequently asked questions
What makes a React Native boilerplate “good” in 2026?
Two things. Clean, shippable infrastructure (auth, payments, analytics, offline-first sync, CI/CD) wired correctly the first time, and a structure your AI tools can actually follow. AI Mobile Launcher ships both: RevenueCat, Supabase, Firebase, MMKV-backed offline-first todos as a reference, plus the U-AMOS 2.0 memory system that keeps Cursor and Claude Code from inventing patterns.
Which version does the Standard tier target?
Expo SDK 55.0.17 with the New Architecture enabled, React Native 0.83.6, TypeScript strict mode. Updated alongside each Expo SDK release.
Does the Standard tier include AI provider integrations?
No. The Standard tier is a clean, AI-free foundation. AI providers (Gemini, OpenAI, on-device llama.rn, multimodal analyser, AI-generated UI) ship in the AI Pro tier.
Is RevenueCat included?
Yes. RevenueCat is wired into both Standard and AI Pro tiers with a pre-built paywall screen, free trial flow, multi-language paywall configurations, A/B variants, restore purchases, and a 48-hour cooldown so users don't get pestered.
Is end-to-end testing included?
No. Jest plus Testing Library are bundled for unit and integration tests, with coverage already in place for auth, todos, and notifications. End-to-end frameworks like Detox are not bundled.
Does it include Supabase?
Yes. The auth feature talks to Supabase out of the box (Apple, Google, Email/Password). The database layer uses Supabase Postgres with row-level security. Tokens live in expo-secure-store. Swap to Firebase Auth or your own API by replacing one client.
How many languages are included?
Three: English, French, Spanish. The device locale is auto-detected on first launch via expo-localization. Adding more languages is a one-file change.