Bare React Native vs Expo in 2026: When to Go Bare

Bare React Native vs Expo in 2026: When to Go Bare

Bare React Native or Expo? A clear 2026 decision grid: when bare is worth it, what Expo now covers, EAS free plan limits, and how to switch safely.

Table of Contents

Bare React Native means a React Native app where you own and edit the native `ios` and `android` folders yourself, with no framework generating them for you. For most new apps in 2026, it is no longer the right place to start: the official React Native docs (environment setup page) recommend starting with a framework, and Expo is the one they name. This guide covers what 'bare' means today, what Expo handles for you, the few cases where going bare is worth it, and how to decide in five minutes. If you're a founder picking a stack for an MVP, you can also book a free 30-minute call and we'll tell you which setup fits your app.

Ready to build?

Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.

What 'Bare React Native' Means in 2026

'Bare' used to mean 'not Expo'. That line is now blurry. Expo's docs (bare projects overview) say that 'all tools and services provided by Expo work great in any React Native app', and that you can add Expo to an existing bare project by installing the `expo` package. So the real question is not 'Expo or React Native'. Expo is React Native. The question is who maintains the native layer: a generator, or your team. You'll see three setups:

  • Expo with Prebuild (CNG): native folders are generated from `app.json` and config plugins, regenerated on demand. All Expo tools work.
  • Bare workflow with Expo: you commit and edit `ios` and `android` by hand, and still use EAS Build, EAS Update and Expo modules.
  • Bare React Native, no Expo: you own everything through the React Native Community CLI, Xcode and Android Studio. No Expo tools unless you add the `expo` package.

Setup and Upgrades

With Prebuild, the native projects are rebuilt from config. Upgrading React Native mostly means bumping the Expo SDK and regenerating. In a bare project, every upgrade touches native files you have edited by hand, and you merge those changes yourself. Most teams underestimate this cost. You write native code once. Keeping it working through React Native, Xcode and Android SDK upgrades is work you repeat.

Native Access: 'Expo Can't Do X' Is Mostly Outdated

The old argument was that Expo couldn't reach the native features you need. In 2026 that's mostly outdated. Expo Go is a sandbox for quick testing. It is not how you ship. If someone tells you 'Expo is limited' because of Expo Go, they are mixing the two up.

  • Expo modules cover common needs: camera, location, notifications, secure storage, biometrics, file system and more.
  • Config plugins let you change native settings (permissions, entitlements, Gradle and Podfile tweaks) without committing native folders.
  • The Expo Modules API lets you write your own native module in Swift and Kotlin inside an Expo project.
  • Development builds replace Expo Go once you add custom native code, so you're not limited to what Expo Go ships with.

Builds, Store Submission and Over-the-Air Updates

EAS Build compiles iOS and Android apps in the cloud, so you don't need a Mac to produce an iOS build. You still need one to run the iOS simulator or build iOS locally. EAS Submit sends the build to App Store Connect and Google Play. Both work with bare projects too. Without Expo, you run Xcode and Gradle yourself, or set up your own CI with signing, certificates and provisioning profiles. EAS Update pushes JavaScript and asset changes to installed apps without a new store build, which is useful when you need a bug fix out fast. Two limits matter:

  • It only changes JS and assets. Any native change still needs a new store build and review.
  • Your updates must respect store rules: fixes and small changes, not a different app.

Expo EAS Free Plan Build Limits (2026)

According to Expo's pricing page, checked on 21 October 2026, the free plan includes the items below. The paid Starter plan is listed at $19 per month plus usage costs. For an MVP, the free tier often covers development, and you can also build locally with `npx expo run:android`, or `npx expo run:ios` on a Mac. Pricing changes, so check the page before you budget. Tooling is a small line in an MVP budget anyway. Scope, platforms and design weigh much more, as our MVP development cost guide explains.

  • 15 Android and 15 iOS builds per month
  • EAS Update for up to 1,000 monthly active users
  • A low-priority build queue
  • A 45-minute build timeout

When Bare React Native Is the Better Choice

Go bare (or use the bare workflow) when at least one of these is true today, not 'maybe later'. Notice what's missing from this list: 'it feels more serious', 'Expo is training wheels', 'we might need Bluetooth one day'. None of those justify the extra maintenance. Not sure your app fits one of these cases? Book a call and send us the feature list. We'll give you a straight answer.

  • Brownfield app: you're adding React Native screens to an existing native iOS or Android app.
  • Deep custom native code: heavy SDKs with complex native setup that no config plugin handles, and your team would rather edit Xcode and Gradle directly than write a plugin.
  • Strict build pipeline: your company requires its own CI, signing and build machines, with full control of every native file.
  • Native experts on the team: you already have iOS and Android engineers who will own upgrades.

A 5-Question Decision Grid

Answer each question. One answer pointing to bare is enough to look closer.

  • Is this a new app, not an existing native one? Yes points to Expo. Brownfield points to bare.
  • Does every native SDK you need have an Expo module, config plugin or npm package with one? Yes points to Expo. No, with writing a plugin not an option, points to bare.
  • Who will own native upgrades for the next two years? Nobody dedicated points to Expo. A native iOS and Android engineer points to bare.
  • Must builds run on your own infrastructure only? No points to Expo. Yes points to bare.
  • Do you want OTA fixes and cloud builds without setting up CI? Yes points to Expo. Not needed points to bare.

Want us to build it?

Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.

A Concrete Example

A founder wants a booking app for fitness coaches: sign up, calendar, payments, push reminders, in-app chat. Every piece has a maintained package that works with Expo (notifications, a payments SDK, RevenueCat for subscriptions). Verdict: Expo with Prebuild. There's no reason to own native folders. Now take a fleet tool that pairs with a custom hardware device through a vendor SDK shipped only as a raw iOS framework and Android AAR, with a long manual setup guide. You can still start in Expo and wrap the SDK with the Expo Modules API. But if the vendor's support only covers a classic native project, a bare workflow can save you a fight. Even then, you keep EAS Build and EAS Update.

Going From Expo to Bare (and Back)

From Expo to bare: run `npx expo prebuild`. It generates the `ios` and `android` folders from your config. From there you can commit them and edit by hand. You keep your JavaScript code, your Expo modules and EAS. The old word for this was 'eject'. Nothing is lost anymore. The trade-off: once you edit native files by hand, regenerating with Prebuild overwrites those edits. Either move your changes into a config plugin, or stop using Prebuild for that project. From bare to Expo: install the `expo` package, start using Expo modules and EAS where they help, and keep your native folders. Later, if your native changes can live in config plugins, you can delete the folders and adopt Prebuild. Expo's docs describe this as incremental adoption, so you don't need a rewrite. This two-way path is the strongest argument for starting with Expo. You can still go bare later. Starting bare means doing maintenance work from day one for flexibility you may never use.

What We Use for Client MVPs

We build iOS and Android apps on an Expo base. Design is included, and we show you progress every week. The code is 100% yours, on your GitHub, and you get 2 weeks of fixes after launch. Your app is Fixed at $3,460, delivered in about 20 days. Still comparing frameworks? Read our React Native vs Flutter guide and our guide to the best tech stack for an MVP. If you built a prototype with an AI tool and it only runs in Expo Go, our AI prototype to production page explains what's missing before the App Store. Want to know which setup fits your app? Book a call.

FAQ: Is Bare React Native Faster Than Expo?

No, not by default. Both run the same React Native runtime and the same JavaScript engine. Performance depends on your code, your lists, images and animations, not on whether a generator creates the native folders.

FAQ: What Is the Difference Between Expo Go and React Native?

Expo Go is a sandbox app for testing an Expo project on your phone, and it only includes a fixed set of native modules. React Native is the framework your app is written in. To ship, or to use custom native code, you make a development build or a store build. Expo Go is never what you ship.

FAQ: Can I Use EAS Build With a Bare React Native Project?

Yes. EAS Build, EAS Submit and EAS Update work in bare projects. You keep your native folders and EAS builds them as they are.

FAQ: What Are Expo's Limits in 2026?

The main limits are practical, not technical. OTA updates can't change native code. The free EAS plan caps cloud builds at 15 per platform per month. And native changes that don't fit in a config plugin mean you maintain native folders yourself. Most native SDKs can be added with a config plugin or the Expo Modules API.

FAQ: Should a Non-Technical Founder Care About Expo vs Bare?

Only for two reasons: the cost of upgrades over time, and who can maintain the app if your developer leaves. A standard Expo project is easier for a new team to pick up. Ask your developer which setup they chose and why, before they start. If you're still choosing who builds your app, our guide to picking an MVP development agency lists the questions to ask.

Ready to build yours?

Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.

Related Articles

Ready to ship your MVP?

Fixed-price builds from $3,460 · Post-launch support from $500/mo

Frequently Asked Questions

Who Is Behind BuildMVPFast?

BuildMVPFast is led by a passionate team of Creators, Designers, and Developers. Together, we deliver innovative software solutions tailored to each client's unique needs. Our vision is to help clients unlock their full potential by providing a rapidly built, high-quality MVP that serves as the perfect launchpad for their business idea.

Who Owns The Code, Design And Intellectual Property?

How Long Does It Take To Build An MVP?

What Is Your Development And Delivery Process?

Do You Offer Post-Launch Support And Maintenance?