For most startup apps, react native expo is the better place to start: Expo handles project setup, builds and updates, so a small team ships to iOS and Android faster. Choose bare React Native only if you need custom native code on day one. Switching later is usually a planned migration, not a rewrite.
| Area | Expo | Bare React Native |
|---|---|---|
| Project setup | One command, tooling preconfigured | You configure iOS and Android projects yourself |
| Native modules | Expo SDK, many community libraries, config plugins, development builds | Full access to any native code, edited directly |
| Over-the-air updates | Built-in route for JavaScript and asset updates | Possible, but you wire up an update service yourself |
| Builds | Cloud builds, no Mac needed for the build step | Local builds; iOS builds need a Mac with Xcode |
| Store publishing | Guided submission tooling | Manual upload from Xcode and Android Studio or your own pipeline |
| Best for | New apps, MVPs, small teams | Apps with deep native requirements, or existing native codebases |
Bare React Native is the core framework with native iOS and Android project folders that your team owns and configures. Expo is a framework and toolset built on top of React Native. It adds the command line tools, a library of device features, file-based routing and cloud services, while still producing a real native app.
Both routes use React and JavaScript or TypeScript, and both produce native components rather than a website in a wrapper, as Carnegie Mellon's introductory course material puts it. That matters for founders: an Expo app is not a lesser kind of app. It is the same technology with more of the plumbing handled for you.
Expo is the official React Native framework, recommended by the React Native team at Meta for production apps on Android, iOS and the web. Its tools are open source under the MIT licence. In practice, "bare" is now the exception you choose on purpose, not the starting point.
That is the same view we take at Axire Infotech when we build cross-platform mobile apps with React Native: one codebase, two platforms, and as little setup overhead as the product allows.
Expo is faster mainly in the first weeks. A new project runs on a real phone within minutes, with no native toolchain to install first. Hot reload shows changes instantly. The saving comes from skipping setup and build configuration, not from the code you write, which is largely the same in both routes.
University course material makes the same point: React Native lets you prototype, develop and deploy mobile apps very quickly using JavaScript that runs natively on iOS and Android, with hot reload showing edits without recompiling everything. Expo is the layer that makes that loop short.
Once your app depends on a specialist native SDK, the gap narrows. You may need a development build, a config plugin or a small piece of native code. That is still possible inside Expo, but you spend time on native detail either way. Expo does not remove native complexity; it postpones it until you need it.
Cost follows speed. Fewer setup hours means a smaller first invoice and an earlier test with users. For a view of what moves a budget beyond the stack choice, see our guide to app development cost and feature complexity.
The old complaint was that Expo could not use custom native code. That is mostly outdated. Today, Expo apps can use native libraries through development builds and config plugins, which edit the native iOS and Android projects for you. The real limit is Expo Go, the quick preview app, which only runs the native code it ships with.

Most startup features are covered: camera, maps, push notifications, in-app purchases, biometrics, file uploads and analytics. Popular community libraries usually offer a config plugin or install steps that fit Expo's workflow. For a booking app, marketplace or internal tool, you rarely meet a wall in the first year.
Bare earns its place in a few cases. Pick it when you need to write or patch native code often, integrate a vendor SDK that ships only manual native install steps, embed React Native in an existing iOS or Android app, or follow unusual build rules set by an enterprise customer.
Be honest about the cost of control. With bare, your team owns every native upgrade, every Gradle and CocoaPods fix and every iOS version change. A two-person startup can lose days to that. A team with a dedicated native engineer may find it routine.
Over-the-air (OTA) updates let you push fixes to installed apps without a new store release. The key limit is the same in both setups: an OTA update can deliver compatible JavaScript and assets, but it cannot add a new native library to an app already installed on a phone.
Expo bundles a ready route for this. Each update is matched to a runtime version, which tells the system which native build it is safe to run on. With bare React Native you can add an update service, but you set up and maintain the wiring and the version rules yourself.
| Change | OTA update? | What you need |
|---|---|---|
| Text, layout or logic bug fix in JavaScript | Yes | Publish an update on the current runtime version |
| New image or other asset | Yes | Publish an update |
| Add or upgrade a native library | No | New binary build and store release |
| Change app permissions or native config | No | New binary build and store release |
| Upgrade React Native or Expo SDK version | Usually no | New build, then new updates on the new runtime |
Two practical rules follow. First, never publish an update that expects native code the installed app does not have; the runtime version exists to stop that. Second, keep store rules in mind: Apple and Google both publish policies for apps that change behaviour after review, so read them before using OTA for anything beyond fixes and content tweaks.
For founders, OTA is most valuable in the weeks after launch, when small bugs surface quickly and a store review round trip feels slow. It is worth having from the first release.
Both routes end at the same place: a signed iOS build for the Apple App Store and an Android build for Google Play. The difference is who produces those builds. With Expo you can use cloud builds. With bare React Native you normally build locally or on a continuous integration service you configure.

| Step | Expo | Bare React Native |
|---|---|---|
| iOS build | Cloud build, no Mac needed for this step | Mac with Xcode, or a CI service with Mac runners |
| Android build | Cloud build | Gradle on your machine or CI |
| Signing credentials | Managed for you, if you choose | Created and stored by your team |
| Submission | Tooling to send builds to both stores | Upload through Xcode or Transporter, and the Play Console |
| Store accounts | Still required: Apple developer account and Google Play developer account | Same |
Neither route removes store review. Apple and Google still check your listing, privacy declarations and app behaviour. Cloud builds reduce friction around certificates and machines, but a rejected build for a missing privacy answer is the same problem in both setups.
If you are still choosing a studio to build and publish for you, these questions to ask a React Native company before you sign cover who holds the store accounts and signing keys. Owning those yourself is a good rule.
Eject when a required native capability cannot be met with Expo's libraries, config plugins or development builds, or when your team needs to change native code regularly. Cost, preference or a vague worry about limits are not reasons. Most teams never need a full ejection.
The word itself is now misleading. Expo lets you generate the native iOS and Android folders from your project configuration, a step called prebuild. Many apps use that and keep Expo tools for everything else. A hard break from Expo is rare.
A caveat: moving to bare is easy when you have kept your native changes minimal and documented. It gets harder if the team has piled up untracked native tweaks. That discipline matters more than the label on your setup.
Imagine a London founder building a booking app for independent physiotherapy studios. Launch features are sign-in, a calendar, push reminders, card payments and photo upload. Each of these has maintained Expo support, so the founder starts on Expo, tests on real phones in week one and shows a clickable build to studio owners early.
Six months on, a studio chain asks for integration with a niche card reader that offers only a native SDK. The team follows the steps above: development build first, then a config plugin, then prebuild. Only if all fail would they go bare. The cost of that later decision is small compared with having started bare for a risk that may never appear.
Choose Expo if your app is a typical product built on common device features and you have a small team. Choose bare React Native if you must control native code from the start, have a native engineer, or are adding React Native to an existing app. When unsure, start with Expo.
Our opinion is plain: for founders in the UK and Northern Europe building a first or second version, Expo is the lower-risk path. The earlier you put a working app in front of customers, the more your budget goes into learning what they want, not into build tooling. Our team in Ahmedabad overlaps with CET afternoons, which keeps review and feedback loops short for European clients.
One thing is not settled: how quickly Expo's newer tooling will close the last gaps for unusual native needs. Check current documentation for any library you depend on before committing, since this area moves fast. If your product is leaning toward a different framework altogether, our React Native vs Flutter comparison for UK startups covers that choice.
Yes. Expo is the official React Native framework, recommended by the React Native team at Meta for production apps on iOS, Android and the web. Production readiness depends more on testing, monitoring and release discipline than on whether you chose Expo or a bare setup.
Yes. You can generate the native iOS and Android folders from an Expo project and keep your JavaScript or TypeScript code. The effort depends on how many native changes you have made. Keeping them documented and few makes a later move a small, planned job.
Not in a way users typically notice. Both produce native components and run your app logic in the same way. Performance problems usually come from heavy lists, large images or unnecessary re-renders. Profile the app on a real mid-range phone before blaming the setup.
Not always. Expo cloud builds can produce the iOS build without you owning a Mac. With bare React Native, you normally need a Mac with Xcode or a CI service that offers Mac machines. You still need an Apple developer account either way.
For most startups, yes. One codebase for two platforms means fewer developers, faster delivery and simpler maintenance. Fully native apps make sense when you need the deepest platform features. For a cost and timeline comparison, read React Native vs native apps: 15 questions answered.
If you are choosing between Expo and bare React Native, the cheapest decision is the one made against your real feature list. We build React Native apps with one codebase for iOS and Android for startups and businesses across Europe, working through discovery, design, development and launch support. See how that works on our app development service page, browse our projects, or look at the full list of services, including UI/UX design.
Send us your feature list and launch date and we will tell you whether Expo fits, or where bare is worth it. We respond to all inquiries within 2 hours during business hours. More guides are on the Axire Infotech blog.
Let's discuss your project and create something amazing together.