React Native & Expo.
One TypeScript codebase for iOS, Android and often the web, with over-the-air updates.
Talk to us about React Native & Expo
Key features
What React Native & Expo does well.
Cloud builds with EAS
EAS Build produces signed iOS and Android binaries on hosted machines, so an iOS build doesn’t need a Mac on every desk.
File-based routing
Expo Router turns the file structure into screens and navigation, and gives every screen a deep link by default.
The New Architecture
Recent React Native releases call native code directly through JSI rather than an asynchronous bridge, and Expo now runs only on it.
Your own native code
The Expo Modules API lets a team write its own native code in Swift and Kotlin when a library doesn’t cover a need.
What we build with it
One codebase, every platform your users are on.
React Native renders native components from a React and TypeScript codebase, and Expo adds the build service, routing and update tooling around it. We use them when a product needs iOS and Android apps that share logic, and often the web too.
Field and staff apps
Mobile apps for people working away from a desk, with offline-aware screens and device features.
Customer and family apps
Apps that let people follow progress, receive notifications and raise requests.
Cross-platform tools
Specialist interfaces that run on phones, tablets and the browser from shared code.
When it’s the right choice
React Native and Expo suit products that need both mobile platforms, want to share code and types with a React web app, and need to ship fixes quickly.
When we’d pick something else
If an app depends heavily on the newest platform features or needs the tightest integration with one operating system, native Swift or Kotlin may be the better fit.
Our React Native & Expo services
How we can help.
New apps
iOS and Android apps built with Expo, often sharing types and logic with a React web app.
Expo SDK upgrades
Planned moves to current Expo SDK and React Native versions, including the switch to the New Architecture.
Store releases
Signing, store listings, build profiles and update channels set up so your team can release without us.
Ongoing support
Crash triage, dependency updates and fixes shipped as store builds or over-the-air updates as each change allows.
How we work
Starting a React Native & Expo project.
Review what exists
Code, data, hosting and the people who maintain it, before any React Native & Expo decision is made.
Agree the approach
A written scope: what changes, what stays, the risks and how we will know it worked.
Build in reviewable slices
Working increments your team can test, rather than one large delivery at the end.
Hand over or stay on
Documentation and access for your team, or a defined support scope if you want us to keep going.
In our own products
SimRhythm.
SimRhythm runs on iOS and iPad, Android and the web from one Expo and React Native codebase, with React Native Skia drawing the monitor traces.
Read the case study ↗
Industries
Where we use it.
- Health & social care Software for care providers, where visits, medication and family updates rely on one accurate record.
- Medical education Simulators and teaching tools that let educators run realistic practice on the devices they already use.
- Property & field services Software for maintenance and field teams, from the first request through inspection, dispatch and payment.
Where AI fits
AI in mobile work.
On-device models
Apple’s Foundation Models framework and Android’s Gemini Nano APIs run smaller models on the phone, for features that must work offline or keep data local.
AI workflow automation ↗Reading photos of documents
Capture a form or label with the camera and pull out the fields, with the image kept for checking.
Document data extraction ↗
Where it stops: On-device models are only on newer phones and are less capable than cloud models, so features need a fallback.
What’s changing
Shifts to plan for.
Dates that affect React Native & Expo projects, checked against the official sources.
August 2026
Google Play targets Android 16
New apps and updates for phones and tablets must target API level 36. Extensions can be requested until 1 November 2026.
April 2026
App Store requires the iOS 26 SDK
Since 28 April 2026, uploads must be built with Xcode 26. Apps can still support older iOS versions; only the build tools changed.
October 2025
React Native drops the old architecture
React Native 0.82 runs only on the New Architecture, so libraries that never moved over block upgrades.
Where it fits
Related expertise.
- Prototyping & validation Test the key task with the people who do it, using a prototype, before committing engineering time.
- Mobile app development iOS and Android apps that work offline, handle device permissions well and ship through the app stores.
- CI/CD pipelines Automated builds, tests and deployments, so every release follows the same checked path.
Common questions
React Native & Expo questions.
Can we publish to the App Store and Google Play?
Yes. React Native apps are native apps. We prepare store builds, listings and signing, and can set up a release process your team can run.
What can over-the-air updates change?
They can update JavaScript and assets without a store release. Changes to native code or permissions still go through the stores, so we plan releases with that in mind.
Further reading
- One codebase, three platforms: iOS, Android and web with Expo Lessons on sharing code, drawing with Skia and handling phone, tablet and desktop layouts from one Expo codebase.
- A database for every pull request: preview environments that work How to give each pull request its own database branch, with safe data, tested migrations and automatic clean-up.
- Awaab’s Law and the software landlords use for repairs What Awaab’s Law asks of the systems social landlords use to log, investigate and repair hazards, and the records they need to keep.