Platform deep dive · React Native

Our honest read on React Native.

The cross-platform framework that lets JavaScript teams ship native mobile without learning a new language. Code-share with the web frontend, hot reload during dev, and a hiring pool that's every React developer on earth.

Best for
  • JS teams going mobile
  • Code-share with React web
  • Expo-based workflows
  • Fast iteration cycles
Not for
  • Heavy native UI (gaming)
  • Apple Watch / CarPlay
  • Sub-30MB binary requirements
  • Pixel-perfect identical UI
React Native earns the work when the team already lives in React on the web and wants to ship mobile without the org-chart cost of hiring a second team. The shared types + tooling across web and mobile is the real win — not the cross-platform code (which is overstated; production RN apps end up with 30%+ platform-specific code). It's the wrong pick when the app needs heavy GPU work or deep native ecosystem integration.
Prizor AITech engineering After ~9 years building on React Native

React Native vs the alternatives

Side-by-side on the 10 dimensions clients actually ask about. No vendor spin — these numbers come from our own builds.

Dimension React Native Flutter Native iOS / Android Ionic / Capacitor Web wrapper
JS team adoption speed
Code-share with web React
UI rendering performance
Native API access
Binary size (iOS) 20+ MB 30+ MB 5–15 MB 40+ MB < 5 MB
Hot reload during dev
Hiring market depth
Time to first screen < 1 day < 1 day 1–2 days < 1 day < 1 day
Watch / CarPlay / Wear OS
Pricing (6-mo build) $60–180k $60–180k $120–300k $40–120k $30–80k

* "Web wrapper" = Capacitor wrapping a PWA. Cheap to start, slow to mature. RN with Expo Router has narrowed the gap with Flutter on dev experience; the choice now is more about team familiarity than platform capability.

When we don’t recommend React Native

React Native is a great tool — for the right job. Here’s where we’d point you elsewhere, even when it costs us the project.

Apple Watch / CarPlay / Vision Pro?

Native iOS (Swift)

RN's reach into Watch / CarPlay / Vision is limited. For deep Apple ecosystem integration, Swift + SwiftUI is the only credible path.

GPU-heavy app (games, AR, video editor)?

Native or Unity / Unreal

RN's JS bridge adds frame latency that's visible on GPU-heavy work. For games, AR, video editing — native or game engines win.

Sub-15MB binary (emerging markets)?

Native or Web wrapper

RN runtime + Hermes engine pushes minimum binary to ~20MB. For markets where binary size matters (data costs, low-end devices), native wins.

Want identical pixel-perfect UI both platforms?

Flutter

RN respects platform conventions (iOS-style on iOS, Material on Android). Flutter renders its own pixels — identical UI everywhere. Different philosophies; pick which one fits your design team.

The stack we’d actually build

A real React Native project rarely lives alone. Here’s the typical integration stack for a production build.

  • Core platform
  • Best-in-class integrations
  • Real-time sync

Total tooling cost: ~$80/mo for a production RN app on Expo EAS Production tier + Supabase Pro + Sentry. Apple Developer ($99/yr) + Google Play ($25 one-time) on top. Most RN MVPs ship in 6–10 weeks; full production apps run 12–20 weeks. JS team familiarity shaves 30–50% off vs adopting Flutter.

What else we can build on React Native

React Native covers everything from internal tools to App-Store-quality consumer apps. Here's what we ship on RN when JS team familiarity + cross-platform speed is the brief.

Expo Router Apps

File-based routing (like Next.js) for RN — type-safe deep links, web-friendly URL patterns.

  • Expo
  • Routing

NativeWind / Tamagui

Tailwind-style styling for RN, or Tamagui for compile-time optimized themed UI.

  • Style
  • Theme

Reanimated 3

60–120fps animations driven on the UI thread — no JS bridge bottleneck.

  • Animation

TypeScript Everywhere

Shared types between mobile and web React clients — bugs caught at compile time.

  • TS

Native Modules

Swift / Kotlin bridges for platform-specific features RN doesn't cover natively.

  • Native

Push Notifications

Expo Push or native FCM/APNs — segmented, scheduled, rich notifications.

  • Push

OTA Updates (Expo)

Ship bug fixes without App Store review — JS-only updates pushed to users in minutes.

  • OTA
  • Expo

Supabase / Firebase

Auth, DB, realtime, push, storage — backend-as-a-service tailored for mobile.

  • BaaS

Custom Node + tRPC

When BaaS isn't enough — type-safe Node backend with tRPC ties to RN.

  • Node
  • tRPC

In-App Purchases

RevenueCat-managed subscriptions across iOS + Android — handles the receipt mess.

  • IAP
  • RevenueCat

AR / Camera Features

react-native-vision-camera, ARKit/ARCore bridges for AR experiences.

  • AR
  • Camera

Don’t see what you’re building? Tell us about it — most of what we ship isn’t on this list.

The actual offer

Two ways we ship React Native work.

The deliverable is the same — production-grade React Native builds backed by ~9 years on the platform. What changes is whose name goes on the project. Pick the engagement model that fits.

For Agencies · White-label

Your name on it. Our hands on it.

We become your invisible React Native team. You stay client-facing; we handle design, build, and delivery.

  • Custom React Native builds to your Figma — or full Figma → React Native end-to-end
  • Your branding on every deliverable; your client never sees our name
  • NDA signed pre-kickoff; collaboration inside your Slack and your Notion
  • Direct line to a senior dev — no handoff to junior offshore
  • Optional white-label maintenance retainer once sites go live

Engagement Hourly or fixed-project. Most agency builds run 2–8 weeks per site, depending on scope.

For End Clients · Direct

From kickoff to handoff. One team.

Full engagement: discovery, design, build, launch, and ongoing care. One point of contact, ~9 years on React Native.

  • Discovery + content audit + scoped proposal in week 1
  • Figma design + React Native build with weekly review cadence
  • CMS / admin training + handoff documentation at launch
  • Performance + SEO + accessibility baseline before sign-off
  • Optional care retainer for ongoing iteration after launch

Engagement Project-based or monthly retainer. Most direct engagements run 4–12 weeks end-to-end.

Not sure which model fits? Most engagements start with a 30-min scoping call where we figure that out together.

Engineering rates · USD

Real engineers. India-priced.

All-in rates for React Native engineers — 3 to 15 years of experience. USD quoted; INR / EUR / GBP available on invoice. Pick your tier and engagement model.

How we calculate this
Hourly
The base. You pay for every hour the engineer logs. No minimum — usually billed in 15-min increments.
Monthly retainer
hourly × 160 hrs/mo × 0.90 — the engineer is dedicated full-time for the month. We discount 10% in exchange for the commitment.
Fixed-cost · scope-first
We don’t quote fixed-cost without scope. After a 15-min scoping call, the typical formula is hourly × estimated hrs with a 10–15% scope-creep buffer absorbed by us. Three months of senior dev typically lands in $15k–$35k depending on platform and complexity — we’ll give you a precise number after we understand the project.
3 – 6 yrs

Mid

$ 22 / hour

React Native developer who ships features with Expo Router and Supabase backend.

Best for
  • MVP development
  • Feature iteration
  • Push notifications + OTA updates
  • App Store / Play deploys
10 – 15 yrs

Lead · Architect

$ 50 / hour

RN architect who designs code-shared web + mobile systems and leads cross-functional teams.

Best for
  • Web + mobile code-share design
  • Performance audits
  • Tech lead + hiring
  • CI/CD + monorepo architecture

Rates in USD. India-based React Native engineers, 3–15 years experience. Monthly retainer = hourly × 160 hrs × 90% (10% commitment discount). 3-month fixed-cost = hourly × 480 hrs of dev time — we absorb scope creep. Excludes Apple Developer ($99/yr) + Google Play ($25 one-time). 6+ month retainers get an additional 10% off.

Still on the fence?

Run the Stack Pressure Test instead.

Answer 12 questions about your project. Get a ranked recommendation across 12 platforms — including React Native, and the four it’s compared against above. Takes about 60 seconds.

Run the Pressure Test

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.

Selected work

Our work on this stack is under NDA.

Every engagement we have shipped on this technology has been delivered for clients under mutual confidentiality. We respect that — and we’d rather walk you through the work in a private session than publish a watered-down case study.

What we share privately
  • Architecture diagrams and decision records
  • Performance / scale metrics (before vs after)
  • Stack-specific gotchas we have solved at production scale
  • Code-review samples (sanitized, with client permission)
How to see it
  • 15-minute discovery call — no pitch deck, no qualification gauntlet
  • Mutual NDA in place before any technical walkthrough
  • Live architecture review on Loom or in-person at our Ahmedabad office
  • References from current retained clients on request
How the work happens

A short, opinionated process. Built around shipping.

Seven phases. Each one independently owned, all connected.

01

Discovery

Week 1

Goals, audience, content, integrations, budget, timeline.

02

Platform rec.

Week 1–2

Honest CMS pick — fits your team, scale, roadmap.

03

Design direction

Week 2–3

Wireframes, system tokens, two visual paths.

04

Build

Week 3–8

Hand-coded blocks, sections, templates. Staging day 3.

05

Optimize

Week 7–8

Lighthouse, Core Web Vitals, accessibility, schema.

06

Launch

Week 8–9

DNS cutover, analytics QA, sitemap submission.

07

Ongoing support

Optional

Retainer for performance, content ops, A/B tests.