Specialist service · react native app development company

React Native development

Yes, for every new app: the New Architecture (Fabric renderer, TurboModules and JSI) has been the default since React Native 0.76, with Hermes as the JavaScript engine.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

When your web team already writes React, a React Native app development company can turn that skill into iOS and Android apps without hiring two native teams. Red Balloon builds React Native apps for EV charging networks, publishers, marketplaces and SaaS products that want shared logic, fast iteration and a native feel. We work in TypeScript with current React Native tooling and automated end-to-end tests, and plan staged over-the-air updates for fixes that do not need a store review. Native modules are written where performance, background tasks or device features call for them. React Native app development cost depends on screens, integrations, offline needs and how much code can be shared with your web product.

What drives React Native app development cost

React Native app development cost depends mostly on how much of the app is shared JavaScript and how much needs native work. Screens, forms, lists and payments through gateways with React Native SDKs are shared and quick to build. Background location, Bluetooth devices, HealthKit, custom camera work or a native SDK without a React Native wrapper need Swift and Kotlin modules, which take longer and need testing on each platform.

Other drivers are the number of screens and roles, offline needs, languages, and whether the app shares packages with an existing web codebase. As a React Native app development company in India, we scope each of these during the Growth Audit and quote the first release with native work listed separately.

Taking over an existing React Native app

Many apps we inherit were built a few React Native versions ago and have drifted. They may still run on the legacy bridge, depend on libraries that no longer support current releases, or ship fixes through a retired over-the-air service. The first job is an audit: React Native and Expo versions, every native dependency, the build pipeline, and crash data from the last few months.

From that we write an upgrade path in steps, each one releasable, rather than a single risky jump. Signing keys and store accounts are moved under your ownership if they are not already. Upgrades then run alongside feature work, so users see improvements while the foundations are repaired.

Where React Native still needs native engineers

React Native lets most of an app run on shared code, but not all of it. Payment SDKs, KYC tools and device integrations used in India are often native-only, and some phone makers handle background work differently. When those gaps appear, someone has to write and maintain Swift and Kotlin modules that the JavaScript layer calls.

Our teams include engineers who work in both worlds, so native modules are built to the same standard as the rest of the app and documented for your team. We keep these modules small and well tested, because they are the parts most affected by each new iOS and Android release.

Where this works

Real-world situations we're built for

Illustrative · not a client
Mobility / EV charging

Delhi EV-charging network's web team knows React; drivers need charger maps, live availability and UPI payment

What we'd do
React Native app on Expo with maps, live charger status over WebSockets and UPI intent payments
What moves
Charging sessions started via app up, failed payment rate down; tracked as failed payment rate before and after, over a fixed period
Media / news

Noida regional news publisher needs Hindi push alerts and fast article loads

What we'd do
React Native app sharing article components with their Next.js site, push via FCM and APNs
What moves
Push open rate up, daily active readers up
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Stack setup

1–2 weeks

Expo or bare decision, New Architecture library audit, CI, environments

You get: Skeleton app and library audit

We need: Repo access and API docs

Build

6–12 weeks

Feature sprints, native modules where needed, Maestro or Detox tests

You get: Internal builds every sprint

We need: Product owner reviews

Release and OTA setup

1–2 weeks

Store submissions, OTA channels, rollback rules; rule of thumb: roll back an EAS Update if crash-free users fall more than 0.5 points

You get: Live apps with an update pipeline

We need: Store accounts and release approvals

A typical engagement

From first call to result

Illustrative · not a client

Gurugram fitness studio chain, 12 locations, bookings on a React web app, 3 frontend engineers

Weeks 1–2SetupExpo on the New Architecture, TypeScript, shared API client, EAS project; check each native library's New Architecture support in React Native Directory firstSkeleton app running on both platforms
Weeks 3–8Core flowsClass schedule, booking, membership payments via Razorpay, push remindersInternal EAS builds every week
Weeks 9–11Beta and store reviewTestFlight and Play closed test with 100 members for two weeks, covering booking, Razorpay payment and push on five low-end Android phonesBoth apps approved
Weeks 12–16OTA and iterateEAS Update channels for JavaScript fixes, HealthKit native module for workout dataWeekly OTA fixes, monthly store builds
Where it starts70% of class bookings on mobile web, no push reminders, 18% no-show rate, many members on iPhone
Where it endsA React Native app the in-house web engineers maintain. Weekly watch: no-show rate, share of bookings via app, crash-free users.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Crash-free usersUsers with no crash or fatal JavaScript error ÷ total usersRule of thumb: hold above 99% crash-free users per release in Sentry release health; pause the OTA rollout if it drops belowSentry for React NativeWeekly
OTA update adoptionUsers on the latest update ÷ active users, 72 hours after publishingSet from first releases, then aim upwardEAS Update insightsEvery update
JavaScript bundle sizeSize of the Hermes bundle per platformSet a budget from baseline and fail builds that exceed itBundle visualiser in CIEvery release
Startup timeTap to first interactive screen, p90, on a budget Android phoneRule of thumb: under 2 s at p90 on a budget Android phone; Android vitals treats cold starts of 5 s or longer as excessiveSentry performance or Firebase Performance MonitoringEvery release
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Release tagCloud builds and submissionsEAS Build and EAS Submit triggered from GitHub ActionsRemoves: Local build failures and manual store uploads
When: Approved JavaScript-only fixStaged OTA rolloutsEAS Update channels with percentage rolloutsRemoves: Waiting on store review for small fixes, or shipping a bad fix to everyone
When: Every pull requestEnd-to-end testsMaestro or Detox flows in CIRemoves: Booking or payment flows breaking silently
Rules we work to

Standards and regulations

AppleApp Store Review Guidelines (software requirements on downloaded code)

OTA updates may fix bugs within reviewed scope but must not change the app's features or primary purpose

GoogleGoogle Play Developer Program Policies (Device and Network Abuse)

Apps may not download executable native code outside Play; JavaScript run by an interpreter is allowed

What's changing

Platform and policy updates that affect this work

We track: React Native blog, Expo changelog.

React Native (Meta)Version 0.76 made the New Architecture the default for new projects

Start new apps on the New Architecture and check every library supports it

MicrosoftVisual Studio App Center, including CodePush, was retired

Apps relying on CodePush need EAS Update or a self-hosted alternative

Before you hire anyone

Questions to ask any agency, including us

Which libraries we need lack New Architecture support, and what's the plan?

Why ask

One incompatible library can stall upgrades

A good answer

A library audit against React Native Directory, with replacements or an interop plan

How will you keep our React Native version current?

Why ask

Version gaps become painful quickly

A good answer

An upgrade cadence, use of the React Native Upgrade Helper, test gates and time budgeted each quarter

Can our web developers maintain this app after handover?

Why ask

Reusing your team's React skills is the main reason to choose React Native

A good answer

Shared conventions with your web code, documentation and paired handover sprints

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Should our app use Expo or bare React Native?

We default to Expo, which the React Native docs recommend as a framework, because EAS Build, config plugins and Expo Router cut setup time; custom native code still fits through development builds.

  • Expo Go is only for prototyping; production apps use development builds that can include any native module.
  • Bare React Native suits heavy custom native code or strict in-house build pipelines. EAS Build is paid with a free tier; builds can also run locally or on your CI.
Can a React Native app be updated without waiting for App Store review?

JavaScript and asset changes can ship over the air with EAS Update in minutes; anything touching native code, permissions or the app's core purpose still needs a full store release.

  • Apple's developer agreement permits downloaded interpreted code only if it doesn't change the app's primary purpose.
  • Microsoft retired App Center, including CodePush, on 31 March 2025; apps still using it need to move to EAS Update or a self-hosted alternative.
  • Updates are tied to a runtime version, so a JavaScript bundle never reaches an incompatible native build.
  • Roll an over-the-air update out to a small share of users first. Without that, a bad bundle reaches everyone within minutes.
Can a React Native app work well in Hindi and other Indian languages?

Yes. React Native handles Unicode text and Indian scripts well, and translation libraries load the right language at runtime. The care goes into layout: Hindi, Tamil and other scripts can run longer or taller than English, so buttons and cards are tested with real translations and large system fonts. Push notifications and store listings need translating too.

  • Indian scripts supported
  • Test layouts with real translations
  • Translate pushes and listings too
Can our web developers really maintain the React Native app?

Mostly, yes. Engineers who know React and TypeScript can work on screens, state and API code within weeks. They will need help with store releases, signing, native crash logs and any Swift or Kotlin modules. We pair with them through handover and leave a runbook, and we can stay on call for native work if you prefer.

  • React skills transfer to screens
  • Native and release work needs support
  • Paired handover and runbook
Back to the service

Mobile app development →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.