React Native development

A React Native app development company that ships iPhone and Android from one codebase

Your JavaScript or TypeScript team gets an app on both stores that it can read, extend and release, with the accounts and the code in your name.

Get a written scope for your React Native app
Trusted by the world's fastest-growing brands

What React Native is

React you already know, rendering real native screens

React Native app development is building an iPhone and Android app from one TypeScript codebase, using React components that draw the platforms’ own interface elements. It suits teams that already write React, and it has limits we will name before you commit.

9:41Next visitThu, Oct 16Note for crewReminderRescheduleHistorySep 25PaidSep 18VisitScreen.tsxone fileiOSAndroid<TextInput>UITextFieldEditText<Switch>UISwitchSwitch<FlatList>UIScrollViewScrollView

One codebase, two stores

Screens, navigation and business rules are written once in TypeScript. Where a platform needs its own behavior, such as a Face ID prompt or an Android back button, the code branches in one place.

Shared with your web app

If a React site already talks to your API, the types, validation and data fetching can move into a shared package. The screens themselves are written fresh, because a phone is not a browser window.

Expo for builds and updates

Expo handles cloud builds, store submission and over-the-air updates. We use development builds with native modules when the app needs them, so Expo doesn’t cap what the app can do.

Choosing the approach

One React Native codebase or two native apps

Both reach the App Store and Google Play. The choice turns on who maintains the app and how much of it leans on the phone’s hardware.

NativeSwift and Kotlin appsReact NativeOne TypeScript codebase
Who maintains itAn iOS developer and an Android developer, each in their platform’s languageWeb and app developers share one language and can move between the two
Shipping a new featureWritten twice, so the two apps can drift apartWritten once, then checked on both platforms
Hardware-heavy featuresDirect access to the newest platform APIs on the day Apple or Google ships themPossible through native modules, with extra work for each platform
A good fit whenCamera processing, augmented reality, Bluetooth devices or custom graphics are the productAccounts, lists, forms, bookings, messaging, payments and content make up most of the app
When we would tell you to go native

If the app’s main value sits in a camera pipeline, a Bluetooth peripheral or a game-style interface, we will recommend native, and Flutter is the other cross-platform option we would put on the table. The written scope records that answer.

The platform and the stores

Six facts that shape a React Native build

Each fact carries its source and the date we read it.

  1. ArchitectureReact Native

    The New Architecture became the default in React Native 0.76.

    The React Native team announced the release on October 23, 2024 and declared the New Architecture ready for production. It is a rewrite of the framework’s internals, and new projects started on it from that version.

  2. UpgradesReact Native

    React Native 0.82 runs entirely on the New Architecture.

    Settings that switched it off are ignored from that version. Teams still on the old architecture are told to move to React Native 0.81 or Expo SDK 54 first, turn the New Architecture on and test, then upgrade. An older app is an upgrade project before it is a feature project.

  3. UpdatesExpo

    Over-the-air updates carry JavaScript and assets, and native changes need a new build.

    Expo’s documentation lists a new app permission, a native dependency change and an Expo SDK upgrade as changes that need a new binary. Bug fixes in JavaScript, copy, translations and layouts can ship as an update.

  4. AppleApp Review

    Apple does not let an app download code that changes its features.

    Guideline 2.5.2 says apps may not download, install or execute code that introduces or changes features or functionality. Expo’s own documentation tells developers that updates must follow the App Store and Play Store guidelines, and that changes to an app’s behavior usually need to be reviewed.

  5. GoogleGoogle Play

    Google Play bars an app from updating itself outside Play, with an exception for interpreted code.

    The Device and Network Abuse policy says an app may not modify, replace or update itself by any method other than Google Play’s update mechanism. It excepts code running in a virtual machine or interpreter that gives only indirect access to Android APIs, such as JavaScript in a webview or browser.

  6. Target APIGoogle Play

    New apps and updates on Google Play must target Android 16 from August 31, 2026.

    That is API level 36, with an extension available to November 1, 2026. A React Native app carries its Android target in the project settings, and Expo SDK upgrades move it, so the target level is part of keeping the app current.

The scope

What a React Native build produces

Six parts of the work, each ending in something you can open.

VisitCard.tsx0 type errors1import { Visit } from '@greenway/shared'2type Props = { visit: Visit }3function VisitCard({ visit }: Props) {4 return <Row title={56 } />7}visit.serviceservice: ServiceType@greenway/sharedUnlock.ios.tsxUnlock.android.tsx

TypeScript app build

Screens, navigation and state written once in TypeScript, with platform-specific code kept in clearly marked files. You receive: the repository in your organization, with a README that a new developer can follow on a clean machine.

React NativeTypeScriptExpo
Shared code mapSample · Greenway@greenway/sharedweb + appPieceWeb portalAPI types and clientSharedBooking and invoice rulesSharedSign-in and tokensPartlyScreens and navigationApp onlyPush notification setupApp only

Code shared with your web app

A shared package for API types, validation rules and data fetching, used by both the React site and the app when your web code is structured for it. You receive: the package, and a note listing what is shared and what is not.

Native modules2 now · 2 laterNowPush reminderBefore crew arrivesNowCard paymentService, not in-appLaterPhoto uploadCamera workLaterLive crew locationLocation services

Native modules where needed

Push notifications, biometrics, payments or a camera feature added through maintained libraries, and a small custom module in Swift or Kotlin when no library fits. You receive: the module list with the reason for each.

EAS releaseproductionBuild1.0 (31)iOS builtAndroid builtApp Store ConnectsubmittedGoogle Play ConsolesubmittedSigning credentialsGreenway’s Expo

Builds and store submission

Cloud builds for both platforms from your Expo account, signing credentials stored in it, and the submissions to App Store Connect and Google Play Console. You receive: the build profiles and the release steps, written down.

EAS BuildEAS Submit
Publish updateAllowedCopy fix, booking screenproductionUpdate policyApp Review 2.5.2JavaScript and assets onlyNo new permissionNo native or SDK changeNew permission: store releasePublish

Over-the-air update rules

A short policy for what may ship as an update and what needs a store release, set against Apple’s and Google’s rules and reviewed with you. You receive: the policy and the channel setup.

Profiler · Galaxy A1 slow listService history, long accountVisitHistoryFlatListHeaderRowRowRowRowRowRowUpgrade planGoogle Play target API 36from Aug 31, 2026React Native + Expo SDK upgradeplanned

Performance and upgrade plan

Startup time and slow-screen checks on mid-range phones, plus a plan for the next React Native and Expo SDK upgrades. You receive: the profiling notes and the upgrade plan.

How it runs

Scope, build, test, release

You sign off on a stage before the following one starts. The store and Expo accounts belong to you from day one.

rn-scope.csv

First version scope

Sample · Greenway Lawn Care customer app
FeatureFirst versionNote
Book and reschedule a visitYesReuses the booking API from the customer portal
Sign-in and service historyYesShares the portal’s auth code
Push reminder before the crew arrivesYesNeeds a native module and permission
Card payment of invoicesYesLawn care is a service delivered outside the app
Photo upload of problem areasLaterCamera work; revisit after launch
Live crew location on a mapLaterLocation services; may justify native modules
Anything that pulls the app toward native work is named here, with the reason.

Our stack

The tools behind a React Native build

What the app is written, tested and released with, and the job each tool does.

React Native
Why React Native

React Native is Meta’s open-source framework for building iPhone and Android apps with React.

How we use it

The app’s screens and logic are React Native components in TypeScript, on the current New Architecture.

Cross-platformEcosystemNative UI
React NativeYes
FlutterCustom
CordovaNo

Questions

React Native development, answered

Start here

Get a written scope for your React Native app

Tell us what your team works in today. We’ll send back the screens, what the app shares with your web code, the native features it needs, and a fixed price for the first milestone.