React Native App

How Much Does a React Native App Cost to Build?

A real cost breakdown for cross-platform iOS and Android apps — Expo, EAS, App Store submission, and what moves the price.

React Native with Expo is the most practical path to both the App Store and Google Play from a single codebase. But 'cross-platform' does not mean 'half the work' — auth, push notifications, offline behaviour, and App Store compliance all need to be handled correctly. Here is what it actually costs, and what drives the price up or down.

Typical price range

$8,000 – $20,000Range for a production iOS app with auth, core feature set, and push notifications. Full cross-platform (iOS + Android) or complex booking/marketplace flows push higher.

Get a custom estimate →

What's included

Standard build scope

Expo project setup and EAS pipeline

Expo SDK configuration, expo-router navigation, EAS Build profiles for development and production, and EAS Submit wired to App Store Connect. OTA update channel configured for post-launch JS patches without going through review.

Authentication

Apple Sign-In (required if any other social login is offered), email/password auth, and optional Google Sign-In — all backed by Supabase Auth. Session persistence, token refresh, and secure credential storage handled correctly.

Core feature screens

All screens defined in scope — home, listings, profiles, forms, dashboards. Navigation structure built with expo-router. Shared design system with platform-appropriate components for iOS and Android.

Push notifications

Expo Push Notification service wired to backend events. Permission request flow, device token management, and notification tap-throughs with deep link routing to the relevant screen.

Offline support

Critical data cached locally so the app remains usable without a connection. Queued actions (form submissions, state changes) sync automatically when connectivity returns.

App Store submission

Provisioning profiles, code signing, privacy manifest compliance, App Store Connect metadata (screenshots, description, keywords), and submission. I handle the review process and resolve rejection feedback through to approval.

What moves the price

Cost variables

A React Native codebase targets both platforms, but Android requires its own Google Play Console setup, signing config, and submission pipeline. Adding Android typically adds $1,500–$3,000 for the build configuration, testing on Android devices, and Play Store submission.

A read-heavy app (browse listings, view profiles, read content) is faster to build than one with complex user interactions (booking flows, multi-step forms, real-time matching). Each significant interactive flow adds $1,500–$3,000 to the project.

Live data updates via Supabase Realtime (booking status changes, chat messages, notifications) add $1,000–$2,500 depending on the number of real-time data channels and the complexity of the update logic.

Displaying a map (react-native-maps), requesting location permission, and geo-filtering results adds $1,000–$2,000 depending on the complexity of the location logic and the map interaction requirements.

Photo upload (profile photos, service photos), camera access, or Face ID / Touch ID authentication each require native permission flows and add $500–$1,500 per feature depending on complexity.

If the app sells digital goods or services within the app, Apple requires In-App Purchase (IAP) — third-party payment processors like Stripe cannot be used for in-app transactions without risking App Store removal. Apple IAP integration adds $2,000–$4,000 and Apple takes a 15–30% commission.

Scope clarity

What's not included

Apple Developer account ($99/year) — required for App Store distribution
Google Play Developer account ($25 one-time) — required for Play Store distribution
Ongoing hosting for the backend (Supabase, API server) — typically $20–$60/month
Apple IAP commission (15–30% of in-app purchase revenue goes to Apple)
App Store Optimization (ASO) — keyword research and listing copy beyond the initial submission
Android-specific testing on physical device fleet beyond standard emulator testing

FAQ

Common questions about cost

Why React Native instead of Swift or building a web app?: Swift gives you the best native performance and deepest iOS integration, but you end up with two separate codebases — one for iOS, one for Android. React Native shares 90%+ of the code between platforms. For product apps (booking flows, directories, dashboards, social features), the performance difference is imperceptible to users. The cost and timeline difference is very real. A responsive web app is cheaper still, but cannot access push notifications, camera, biometrics, or offline storage in the same way — and it will not be found on the App Store.
Can I use Stripe for payments in a React Native app?: It depends on what you're selling. Stripe is fine for payments on your website or for physical goods and services booked through the app. Apple requires IAP (In-App Purchase) for any digital goods or subscription services sold within the app itself — using Stripe for those transactions risks having your app removed from the App Store. If your app is a companion to a web platform and the actual payment happens on the web, Stripe is fine.
How does the App Store review process work and how long does it take?: You submit a build through App Store Connect and Apple reviews it — typically within 24–48 hours for a new submission. Common rejection reasons I've encountered and resolved: missing privacy manifest entries, incorrect Apple Sign-In button implementation, and missing account deletion functionality. I stay hands-on through the review process and handle any rejection feedback. Most apps get approved within 3–5 days of first submission; apps with rejections typically resolve within a week.
What are OTA updates and when can I use them?: Expo's EAS Update lets you push JavaScript and asset changes to users' devices without going through App Store review. This covers UI tweaks, bug fixes, and content changes. Changes that touch native code — new device permissions, new native libraries, or changes to the app binary — still require a full build and App Store submission. OTA updates are the right tool for fast iteration after launch; new native features are not.
Do you offer payment plans?: Yes — 40% at kickoff, 30% when the TestFlight build is delivered for your review, 30% at App Store approval. I don't take the final payment until the app is approved and live.

Ready to get a real number?

Describe what you want to build. I'll reply within 48 hours with a scoped estimate — no vague ranges, no sales call required.