Expo
A React Native framework: native projects from config, over-the-air updates and ready-made modules.
Mobile appsUsing since 2020 · Featured project: Hollywood Hair
- Category
- Mobile apps
- Using since
- 2020
- Featured project
- Hollywood Hair
In practice
I pick Expo for React Native apps when the native projects should come from configuration, not from manual work in Xcode and Android Studio. At Blanket I used Expo SDK and biometrics, and at Hollywood Hair it is part of an app with bookings.
What is Expo?
Expo is a framework for React Native apps and a set of services around it. New React Native apps are best started from a framework, and Expo is one: file-based routes, libraries for device features, and plugins that change native code without hand-editing its files.
The iOS and Android projects do not have to sit in the repository. The prebuild command generates them from the app configuration, though using it is optional. Changes in JavaScript and assets alone reach users through Expo Update, between store releases.
- Foundation
- React Native
- Native projects
- Generated by the prebuild command
- Updates
- OTA: JavaScript and assets
- Routing
- Expo Router, routes from files
How I work with Expo
I start with what the app must do natively: camera, notifications or biometrics. That decides whether Expo SDK modules are enough, or whether I have to write custom code.
Libraries and configuration
I install libraries with the expo install command, which picks a version that matches the project. Native settings stay in the app configuration. On Blanket Expo SDK served faster releases and updates.
Biometrics and a development build
I handle fingerprint and Face ID through
expo-local-authentication, as on Blanket. Face ID does not work in Expo Go, so I check it on a development build.Updates and releases
I ship JavaScript fixes through Expo Update, with no new store submission. A native code change needs a new build, so before a fix I check what it touches.
When it fits, and when it doesn't
Expo fits where a React Native app should be maintained without manual work in the native projects.
A good fit when
- A new iOS and Android app in React Native and TypeScript.
- An app whose fixes should reach people between store releases.
- Biometric sign-in or a camera from ready modules.
- A small team that does not want to maintain its own build scripts.
Not a fit when
- An app where most of the work is custom native code.
- A project with its own build process that has to stay as it is.
- A native code fix that has to arrive without a new build: an OTA update will not deliver it.
When full control over the native files is needed, I choose plain React Native.
Expo or plain React Native?
Expo runs on React Native, so you are not choosing between two libraries. You choose who runs the native projects and how the app reaches users.
| Criterion | Expo | React Native |
|---|---|---|
| Native projects | Generated from configuration | Kept by hand in the repository |
| Native changes | Configuration plugins | Editing in Xcode and Android Studio |
| Navigation | Expo Router, routes from files | A library you pick separately |
| Fixes without a store | Expo Update, JavaScript and assets | Depends on the service you pick |
| Project start | Template and libraries ready | You assemble the skeleton yourself |
| Version upgrades | Template and plugins, less work | Native files changed by hand |
Choose Expo when
you start a new app and want the native projects to follow from configuration. You pay by adding your own native code through plugins, not straight in the files.
Choose plain React Native when
you already have a native project or need full control over its files. You get that control, but navigation, libraries and version upgrades are on you.
On Blanket I used Expo SDK and biometrics through Expo Local Authentication, and on Hollywood Hair Expo belongs to an app with bookings and Firebase.
Frequently asked questions
Should the app reach the stores faster?
Describe which device features you need and how often you plan fixes. I will say whether Expo is enough, or whether some of it has to be written natively.