Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 38 ยท Getting Started

What Is Expo?

Learn what Expo is, how it relates to React Native, what the SDK, Expo Router, EAS and Expo Go each do, and when Expo is the right way to build a mobile app.

React Native lets you build iOS and Android apps with React and JavaScript. But a real app is more than components: you need a bundler, a way to run the app on a phone, native code for the camera and notifications, signing keys, store builds and updates. Expo is the framework and set of services that handles all of that around React Native, so you write mostly TypeScript and still ship real native apps.

This lesson explains the pieces, how they fit together and when Expo is the right choice. The real Expo tools (the CLI, simulators, native builds) cannot run inside a web page, so code that needs them is shown read-only. The live examples are small stand-ins that model the ideas in plain JavaScript and clearly say so.

React Native and Expo

React Native itself is the rendering engine. It maps components such as <View> and <Text> to real native views (UIView on iOS, android.view.View on Android) and runs your JavaScript on a JS engine called Hermes. Expo sits on top:

  • Expo SDK: a large set of libraries (expo-camera, expo-location, expo-file-system, ...) with one consistent API for iOS, Android and web. Each library ships its own native code.
  • Expo Router: file-based routing and navigation. See File-Based Routing.
  • Expo CLI and Metro: starts the dev server, bundles your JavaScript and serves it to your phone with Fast Refresh.
  • Continuous Native Generation (CNG): the ios/ and android/ folders are generated from your config and can be thrown away and recreated. See Prebuild and Config Plugins.
  • EAS (Expo Application Services): cloud services for building binaries, submitting to the stores and pushing over-the-air updates.
  • Expo Go: a ready-made app from the stores that runs your project instantly, without compiling anything.

The Expo stack

React Native Native views from React
Expo SDK Camera, files, location
Expo Router Files become screens
EAS Build, submit, update
1 / 2

The key idea: JavaScript versus native binary

Every Expo app has two layers. The native binary (an .ipa or .apk) contains the native code of React Native and of every library you installed. The JavaScript bundle contains your own code. During development the bundle comes from your laptop over Wi-Fi; in production it is embedded in the binary and can optionally be replaced by an update.

This split explains a rule you will meet often: JavaScript changes can be shipped instantly, native changes need a new binary. Adding a screen is a JS change. Adding a library that has native code (say, a Bluetooth module) is a native change, because the binary has to contain that module.

JS Does this binary support my project?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Expo Go contains a fixed list of SDK modules, so a project that needs a custom native library needs its own development build: your own Expo Go with your libraries baked in. See Running on Devices.

One codebase, several platforms

Expo projects target iOS, Android and the web from the same code. Platform differences are handled with Platform or file extensions (Button.ios.tsx, Button.android.tsx, Button.web.tsx):

TSX
import { Platform, StyleSheet } from 'react-native';

const styles = StyleSheet.create({
  card: {
    padding: 16,
    ...Platform.select({
      ios: { shadowColor: '#000', shadowOpacity: 0.15, shadowRadius: 8 },
      android: { elevation: 4 },
      default: { boxShadow: '0 2px 8px rgba(0,0,0,0.15)' },
    }),
  },
});
JS Platform.select, re-implemented

Press Run (or Ctrl + Enter) to see the console output here.

No output.

When to choose Expo

Expo is today the approach the React Native team itself recommends for new apps. It is a good fit when you want:

  • a fast start (one command creates a runnable app),
  • typed, maintained libraries for common device features,
  • builds in the cloud without installing Xcode and Android Studio for every machine (you still need them for local builds),
  • over-the-air updates for bug fixes,
  • web and mobile from one codebase.

It is less natural when your app is mostly existing native code with a little React Native inside ("brownfield"). Even then, you can use individual Expo libraries. Expo apps are not limited: if a library needs native code, you add it and make a development build.

Many old articles say Expo is a "limited sandbox" and you must "eject" to use native code. That was the old managed/bare split. Today, prebuild and config plugins mean you rarely leave Expo at all.

The development loop

  1. Create a project with npx create-expo-app@latest.
  2. Start it with npx expo start.
  3. Open it on a device, simulator or browser.
  4. Edit a file; Fast Refresh updates the screen in about a second.
  5. When you are ready, build with EAS and publish.

You will do steps 1 to 4 in the next two lessons: Create Your First App and Running on Devices.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which part of an Expo app must be rebuilt as a new binary when you add a library with native code?

    Native code lives in the binary. A new native module means a new binary (a development build or production build).
  2. 2. What is Expo Go?

    Expo Go is a ready-made native app containing the SDK modules, so you can run JavaScript instantly.
  3. 3. What does EAS provide?

    EAS (Expo Application Services) builds binaries, submits them to the stores and publishes updates.
  4. 4. Which statement about Expo today is accurate?

    Expo is built on React Native. Prebuild and config plugins let you add native code in the same project.

Summary

  • Expo is a framework and service suite built around React Native: SDK libraries, Expo Router, the CLI, CNG and EAS.
  • An app is a native binary plus a JavaScript bundle; JS changes ship instantly, native changes need a new binary.
  • Expo Go runs a fixed set of modules; development builds contain exactly the modules you need.
  • One codebase targets iOS, Android and web, with Platform for differences.

Next: Create Your First App