New Architecture (Fabric + TurboModules), TypeScript end-to-end, native modules in Swift and Kotlin. Code-share with web where it earns its keep. Production at every scale from 10K MAU to 5M.
Why teams pick React Native (and when they shouldn’t)
Our React Native engagements typically come from teams already shipping React on the web — they want to extend that capability and team to mobile without doubling the headcount. The math works: a senior React dev becomes a productive React Native dev in about three weeks with mentorship, vs three months pivoting to Flutter or six months to native.
Where React Native is the wrong call: apps with heavy native-UI requirements that Fabric still struggles with (complex camera, AR, multi-track video editing), apps where every millisecond of JS-bridge latency matters, and apps with sub-50MB binary-size requirements. We’ll tell you when to pick Flutter or native instead.
What we build
Setup
Expo (managed or bare workflow) for greenfield apps when EAS Build is acceptable for the team. Bare React Native for projects that need deeper native-module work from day one. New Architecture (Fabric renderer + TurboModules) by default — the old bridge is end-of-life and we don’t ship on it.
State + navigation
Redux Toolkit or Zustand for global state, React Query / TanStack Query for server state. React Navigation 7+ for typed routing with deep links. AsyncStorage or MMKV for local persistence. We avoid Context API for anything non-trivial — it doesn’t scale to real product complexity.
Native bridge work
Custom TurboModules written in Swift and Kotlin when the project needs APIs RN doesn’t ship out of the box — biometrics, advanced camera, payment SDKs, Bluetooth LE. Native UI components via Fabric where performance demands it. Same team writes the Dart-equivalent and the Swift/Kotlin — not different vendors.
Code-share with web
Shared TypeScript packages between web (React) and mobile (RN). React Native Web when a third platform target makes sense. Monorepo via Nx, Turborepo, or pnpm workspaces. Domain logic, API clients, type definitions, business rules — all written once.
Distribution
EAS Build + EAS Submit for managed-workflow apps. Self-hosted CI via Bitrise, Codemagic, or GitHub Actions with macOS runners for bare projects. Over-the-air updates via EAS Update or AppCenter CodePush for fast patch cycles between binary store releases.
Where React Native earns the choice
- Teams already shipping React on the web who want mobile parity without doubling headcount
- Apps needing tight code-share between web and mobile experiences
- Projects with native-module needs that justify regular Swift / Kotlin work alongside the JS
- Tight-timeline MVPs where Expo’s developer velocity matters more than maximum performance
- Migrations from Cordova / Ionic / hybrid frameworks to a real native architecture
Pricing
- MVP RN app (managed Expo, single happy-path): $35K–$85K, 10–14 weeks
- Full v1.0 cross-platform app (bare workflow, native modules): $80K–$220K, 16–28 weeks
- Refactor of existing RN app (New Architecture migration, perf rewrite): $25K–$90K, 6–14 weeks
- Cordova / Ionic to RN migration: $40K–$150K depending on app size, 10–20 weeks
Start an RN build
Tell us about the app — what it does, current state, target launch date. connect@prizorai.com or the form. Most of our RN work is under NDA; references happen privately.