Blog

Insights

Expo vs React Native: What's the Difference?

Expo vs React Native explained: Expo is a framework built on React Native. Compare setup, native code, EAS builds and Expo pricing, and see when to skip Expo.

Writer

Nafis Amiri

Co-Founder of CatDoes

Minimal Expo vs React Native comparison illustration featuring both logos, a smartphone mockup, and a VS symbol on a white perspective grid background, highlighting the differences between the two mobile app development tools.

Expo and React Native aren't rivals. React Native is the open-source framework, created at Meta, that turns React code into native iOS and Android apps. Expo is a framework built on top of React Native. It adds file-based routing, a library of native modules, cloud builds and over-the-air updates. Every Expo app is a React Native app.

So the Expo vs React Native question comes down to using React Native with Expo or without it, which developers call "bare" React Native. For most new apps the answer is Expo, and React Native's own documentation recommends it. Below is what each one gives you, how they differ, what Expo costs, and the few cases where skipping Expo still makes sense.

We work with Expo every day: every mobile app CatDoes builds is a React Native app on Expo. Versions and prices in this guide match Expo SDK 58 and React Native 0.88.

Key takeaways

  • React Native is the core. It renders real native views from React components written in JavaScript or TypeScript.

  • Expo sits on top of it, the way Next.js sits on top of React. It adds Expo Router, a standard library of native modules and tooling for builds and updates.

  • The React Native docs recommend starting new apps with a framework and name Expo. You can still start without one.

  • Expo no longer locks you out of native code. Development builds and config plugins run any React Native library. Only the Expo Go sandbox app is limited.

  • The Expo framework is free and MIT licensed. Its cloud services (renamed from EAS in November 2026) have a free tier with 15 Android and 15 iOS builds, and paid plans from $19 a month.

  • Skip Expo mainly when you're adding React Native to an existing native app or targeting Windows or macOS.

Table of Contents

  • What Is React Native?

  • What Is Expo?

  • Expo vs React Native: Key Differences

  • Why the React Native Docs Recommend Expo

  • Can Expo Use Custom Native Code?

  • Expo Build, Submit and Update (Formerly EAS)

  • How Much Does Expo Cost?

  • Is Expo Slower Than Plain React Native?

  • When to Use React Native Without Expo

  • Build an Expo App Without Writing the Code

  • FAQ

What Is React Native?

React Native is an open-source framework for building iOS and Android apps with React. You write components in JavaScript or TypeScript, and React Native renders them as native views, not as a web page inside an app. Meta created it, and the current release is React Native 0.88 from October 2026.

React Native gives you the core pieces: components like View, Text and ScrollView, styling, and the layer that talks to iOS and Android. Since version 0.82, it runs entirely on the New Architecture, its rebuilt rendering and native-module system.

What it doesn't give you is everything around that core. There's no built-in router, no cloud build service, no update system and only a small set of device APIs. Without a framework, you pick and wire up those parts yourself.

React Native runs some of the biggest apps around. Its official showcase lists Facebook and Instagram from Meta, Office, Outlook, Teams and Xbox Game Pass from Microsoft, and Shopping, Alexa and Kindle from Amazon. If you're still choosing between frameworks, our Flutter vs React Native comparison covers that decision.

What Is Expo?

Expo is an open-source framework for apps that run natively on Android, iOS and the web, built on React Native. It plays the role for React Native that Next.js plays for React. The framework and the Expo SDK are free under the MIT license.

The current release is Expo SDK 58, which shipped in October 2026 with React Native 0.88. Here's what Expo adds on top of React Native:

Part of Expo

What it does

Expo SDK

A standard library of native modules for the camera, location, notifications, files and more

Expo Router

File-based navigation for React Native and the web. Each file in your app folder becomes a screen

Expo CLI

Commands to create, run and build projects, starting with npx create-expo-app

Expo Go

A sandbox app for trying a project on your phone by scanning a QR code

Development builds

Your own version of Expo Go, with any native library you need

Continuous Native Generation (CNG)

Generates the ios and android folders when they're needed, while config plugins change native settings for you

Expo Services

Optional cloud tools for building, submitting and updating apps. Until November 2026 they were called EAS (Expo Application Services)

Diagram showing how Expo sits on top of React Native: your app code, then the Expo layer, then React Native, then iOS and Android, with optional Expo Services in the cloud

Bare React Native skips the Expo layer, so you build or pick those pieces yourself. Your components, styles and hooks look the same either way.

Expo vs React Native: Key Differences

The short version is that Expo handles setup, native configuration, builds and updates, and bare React Native leaves them to you. Your app code is the same React Native code in both.


React Native without Expo ("bare")

React Native with Expo

What it is

The core framework

A framework and tools built on React Native

License

MIT, free

MIT, free (cloud services optional)

Start a project

npx @react-native-community/cli@latest init MyApp

npx create-expo-app@latest

Navigation

Pick and set up a library

Expo Router included

ios and android folders

You maintain them by hand

Generated when needed (CNG)

Native libraries

Any

Any, in a development build

Native settings

Edit Xcode and Gradle files

Config plugins in app.json

Cloud builds and store submission

Set up your own (Xcode, Android Studio, CI)

Expo Build and Expo Submit, or build locally

Over-the-air updates

Add an update service

Expo Update (free up to 1,000 monthly users)

iOS builds without a Mac

No

Yes, with cloud builds

Testing on your phone

Install a build or use a simulator

Scan a QR code in Expo Go or a development build

Best for

Existing native apps, Windows and macOS targets

Most new apps

Both setup commands come straight from the React Native docs:

# React Native with Expo (the recommended start)
npx create-expo-app@latest

# React Native without a framework

# React Native with Expo (the recommended start)
npx create-expo-app@latest

# React Native without a framework

# React Native with Expo (the recommended start)
npx create-expo-app@latest

# React Native without a framework

# React Native with Expo (the recommended start)
npx create-expo-app@latest

# React Native without a framework

If you go the Expo route, our create-expo-app guide walks through templates, project structure and your first build.

Why the React Native Docs Recommend Expo

Since June 2024, the React Native team has told developers to start new apps with a framework, and Expo is the one it names. The Get Started page says "most developers benefit from using a React Native Framework like Expo" and calls Expo "a production-grade React Native Framework."

React Native's Get Started page recommending a framework and showing the section Start a new React Native project with Expo

The path without a framework hasn't gone away. The same page says you can use React Native without one, "however, if you're building a new app with React Native, we recommend using a Framework."

Two things explain the close fit. The page notes that "the Expo team works in close collaboration with the React Native team at Meta," and Expo engineers co-write React Native release posts. Expo is also a founding member of the React Foundation, which now governs React and React Native.

Developers have followed the recommendation. In the State of React Native 2025 survey, an independent survey run by Software Mansion, 82% of respondents who started from a template used create-expo-app. 71% used Expo Router for navigation.

Can Expo Use Custom Native Code?

Yes. The old rule that Expo can't run custom native code, and that you have to "eject" to get it, is out of date. Expo dropped the split between "managed" and "bare" workflows. Its glossary now marks those terms as deprecated, because every project uses the same CNG setup.

The limit people remember belongs to Expo Go, not Expo. Expo Go comes with a fixed set of native libraries, and there's no way to add native code it doesn't already include. Each Expo Go build also supports only one SDK version.

For anything beyond that, you make a development build. It's a debug build of your own app that includes the native libraries your project uses. Expo's docs call it "your own version of Expo Go" and recommend it for any app you plan to ship to the stores.

Expo documentation page introducing development builds as your own version of Expo Go where you can use any native library
npx expo install expo-dev-client
npx expo run:ios        # build locally with Xcode
eas build --profile development --platform ios   # or build in the cloud
npx expo install expo-dev-client
npx expo run:ios        # build locally with Xcode
eas build --profile development --platform ios   # or build in the cloud
npx expo install expo-dev-client
npx expo run:ios        # build locally with Xcode
eas build --profile development --platform ios   # or build in the cloud
npx expo install expo-dev-client
npx expo run:ios        # build locally with Xcode
eas build --profile development --platform ios   # or build in the cloud

Native settings like permissions go through config plugins instead of hand edits to Xcode or Gradle files. This snippet in app.json adds the camera permission text for iOS:

{
  "expo": {
    "plugins": [
      ["expo-camera", { "cameraPermission": "Allow $(PRODUCT_NAME) to access your camera" }]
    ]
  }
}
{
  "expo": {
    "plugins": [
      ["expo-camera", { "cameraPermission": "Allow $(PRODUCT_NAME) to access your camera" }]
    ]
  }
}
{
  "expo": {
    "plugins": [
      ["expo-camera", { "cameraPermission": "Allow $(PRODUCT_NAME) to access your camera" }]
    ]
  }
}
{
  "expo": {
    "plugins": [
      ["expo-camera", { "cameraPermission": "Allow $(PRODUCT_NAME) to access your camera" }]
    ]
  }
}

For your own Swift or Kotlin code, the Expo Modules API lets you write a native module that plugs into the same setup. Expo's docs are direct about libraries: "Any library that is compatible with React Native is compatible with the Expo project when you create a development build." To check Expo Go support, filter React Native Directory by "Expo Go".

Expo Build, Submit and Update (Formerly EAS)

Expo Services are optional cloud tools for shipping your app. On November 12, 2026, Expo renamed EAS to Expo Services. The eas command and the eas.json config file kept their names, so older tutorials still work.

Service

What it does

Expo Build (was EAS Build)

Compiles and signs your iOS and Android apps in the cloud

Expo Submit (was EAS Submit)

Uploads your build to the App Store or Google Play with one command

Expo Update (was EAS Update)

Pushes JavaScript fixes straight to users without a new store release

Expo Workflows (was EAS Workflows)

Runs CI/CD jobs for building, testing and releasing

Two details trip people up. First, these services work with any React Native app, even one that doesn't use the Expo framework. Expo's docs say "all tools and services provided by Expo work great in any React Native app." So bare React Native apps don't need a separate update service.

Second, cloud builds remove the Mac requirement for iOS. Apple's tools only run on macOS, but Expo Build compiles your iOS app on Expo's servers, and Expo Submit works from Windows and Linux. You still need an Apple Developer account to publish.

They're widely used, too: 68% of State of React Native 2025 respondents built their apps with EAS Build.

How Much Does Expo Cost?

The Expo framework and SDK are free and open source. You pay only if you use Expo Services beyond the free tier, and you can skip them entirely by building locally with Xcode and Android Studio. Here's what Expo's pricing page lists:

Plan

Price

Included builds

Over-the-air updates

Worth knowing

Free

$0

15 Android and 15 iOS builds

Up to 1,000 monthly active users

Low-priority queue, 45-minute build limit

Starter

$19/month + usage

$45 of build credit

Up to 3,000 monthly active users

High-priority queue, larger build machines

Production

$199/month + usage

$225 of build credit

Up to 50,000 monthly active users

15 concurrent builds, single sign-on

Enterprise

Custom

$1,000 of build credit

Volume pricing

Service level agreements

Expo pricing page showing the Free, Starter, Production and Enterprise plans

Builds past your included amount cost $1 to $2 each for Android and $2 to $4 for iOS, depending on the machine size. Included resources reset each billing period.

The free queue is the main catch. Expo warns that low-priority builds can wait 90 minutes or more at busy times. Store fees are separate either way: $99 a year for the Apple Developer Program and a one-time $25 for a Google Play developer account.

Is Expo Slower Than Plain React Native?

No. An Expo app is a React Native app, so it renders with the same engine and runs the same code at the same speed. Speed differences come from your code and the libraries you add, not from Expo itself.

The slow and bloated reputation comes from Expo's early years and from Expo Go. Expo Go ships a fixed set of native libraries for every project. A development or production build includes only the native libraries your project installs.

App size claims online range from "25 MB for a Hello World" to "2 to 4 MB larger" to "no difference." None of the top-ranking pages making those claims shows a test. If size matters for your app, build it and check the store size report rather than trusting a number from a blog post.

When to Use React Native Without Expo

Bare React Native still makes sense in a few specific cases. Most of the old reasons, like Bluetooth, custom SDKs or background tasks, now work in Expo with a development build and a config plugin.

Your situation

Pick

A new app, MVP or side project

Expo

You need custom Swift or Kotlin code

Expo, with a development build and the Expo Modules API

You need iOS builds but don't own a Mac

Expo, with Expo Build in the cloud

You're adding React Native screens to an existing native iOS or Android app

React Native without the Expo framework

You're building for Windows or macOS desktop

React Native without Expo (react-native-windows or react-native-macos)

An existing bare app with years of native changes

Stay bare, and add Expo modules or services where they help

Existing native apps are the clearest case. If your iOS and Android apps already exist and you're adding React Native screens, you follow React Native's "Integration with Existing Apps" guide. You can still install Expo libraries and use Expo Services in that setup.

If we were starting a React Native app from scratch today, we'd pick Expo, and it's what CatDoes uses for every app it builds. Starting with Expo costs you nothing later, since npx expo prebuild hands you the native folders whenever you want them.

Build an Expo App Without Writing the Code

Everything above assumes you or your team will write the React Native code. If you'd rather describe the app and have it built for you, that's what CatDoes does (it's our product). CatDoes is an AI agent that builds mobile apps and websites from a plain-English description, and every mobile app it builds runs on React Native and Expo.

CatDoes documentation page stating that every mobile app built with CatDoes uses React Native Expo

Here's how the Expo pieces from this guide show up in CatDoes:

  • You describe the app in the chat. The agent writes the React Native and Expo code and connects a backend from CatDoes Cloud, with a database, auth, file storage, edge functions and realtime.

  • You preview it in the browser, or scan a QR code to run it on your phone in Expo Go.

  • When it's ready, you ask for an iOS or Android build. A build takes 10 to 30 minutes and runs on your own Expo account, and a free one works.

  • For iOS, the agent can submit the build to the App Store, and you choose TestFlight or a public release. For Android, you download the build and upload it to Google Play yourself.

  • On the Plus plan and above, you can export the code as a standard React Native Expo project and keep building it with Expo CLI.

In the example above, the preview labels each screen by its Expo Router route (/ (index), /activity, /plan), and the agent asks whether to publish to the App Store or send the build to TestFlight first.

You don't need Xcode or Android Studio installed. App Store and Google Play builds need the Starter plan or above, plus an Apple Developer account for iOS. You can start on the free plan and try the app on your phone before you pay for anything.

Build your Expo app with CatDoes

FAQ

Is React Native still relevant in 2026?

Yes. The react-native package was downloaded about 22.4 million times in the week of November 13 to 19, 2026, according to npm. Meta, Microsoft and Amazon all use it in production, and Microsoft says more than 40 Office experiences are built with it, including Copilot in Office. React Native 0.88 shipped in October 2026, and 86% of State of React Native 2025 respondents agreed it's moving in the right direction.

Is Netflix using React Native?

There's no public evidence that Netflix's current apps are built with React Native. Netflix isn't on React Native's official showcase, and it hasn't said its iOS or Android apps use it. A Netflix engineer did talk about React Native libraries at a 2016 meetup. For well-known examples, the showcase lists Facebook, Instagram, Microsoft Office, Outlook, Teams, Xbox Game Pass, Amazon Shopping, Alexa and Kindle.

Can I use React Native with Expo?

Yes, because every Expo app is a React Native app. You write the same React Native components, and any library that works with React Native works in an Expo development build. The Expo Go sandbox app only runs the native libraries bundled into it, so check React Native Directory's "Expo Go" filter if you want to test there.

Is Expo free or paid?

Both. The Expo framework and SDK are free and open source under the MIT license. Expo's cloud services have a free plan with 15 Android and 15 iOS builds and over-the-air updates for up to 1,000 monthly active users. Paid plans start at $19 a month for Starter and $199 a month for Production, plus usage.

What is Expo Go used for?

Expo Go is a free app for iOS and Android that runs your project on a real phone while you develop. You start the dev server with npx expo start and scan the QR code. It only includes a fixed set of native libraries and supports one SDK version per build, so it's for learning and quick tests, not for shipping. Our Expo Go QR code guide covers scanning and common errors.

Do I need a Mac to build an iOS app with Expo?

No. Expo Build compiles your iOS app on Expo's servers, and Expo Submit uploads it to the App Store from Windows or Linux. You still need an Apple Developer account, which costs $99 a year. Without Expo, iOS builds need Xcode, which only runs on macOS.

Can I move from Expo to bare React Native later?

Yes. Running npx expo prebuild generates the ios and android folders, and you can commit them and edit them by hand from then on. Your Expo libraries keep working. It goes the other way too: a bare React Native app can install the expo package and use Expo modules and Expo Services.

Should beginners learn React Native or Expo first?

Learn them together. Expo is how most developers start with React Native now, and the components, styles and hooks you write in an Expo project are plain React Native. Our React Native Expo tutorial walks through a first app from setup to a production build.

Writer

Nafis Amiri

Co-Founder of CatDoes