🚀 Expo vs Bare React Native

The Two Paths

When starting a React Native project, you have two main approaches: Expo and Bare React Native. Think of it like buying a car — you can get a fully-loaded model with all the features included, or you can get a base model and add what you need yourself.

Both paths lead to production apps — the difference is in the development experience

What is Bare React Native?

Bare React Native (sometimes called "vanilla" React Native) is the framework as Meta provides it. You get:

• The core React Native framework
• Full access to the ios/ and android/ native folders
• Complete control over native configuration
• The need to manually integrate every native feature

It's like getting a house with just the foundation and framing — you add the plumbing, electrical, and HVAC yourself. Maximum flexibility, maximum work.

What is Expo?

Expo is a platform built on top of React Native. It provides:

• A pre-configured development environment
• The Expo SDK — dozens of pre-built native modules
• Expo Go — an app for testing without native builds
• EAS (Expo Application Services) — cloud builds, updates, and submission
• Expo Router — file-based navigation

It's like getting a fully-furnished house. You can still renovate and customize, but you can also move in and start living immediately.

The Evolution of Expo

If you've heard negative things about Expo, they're probably outdated. Expo has evolved dramatically, and the platform of 2024 is fundamentally different from the Expo of 2018 or 2020.

A Brief History

timeline
    title Expo Evolution
    2016 : Expo Founded
         : Managed workflow only
         : Limited native access
    2018 : Expo SDK grows
         : Still no custom native code
         : "Ejecting" was common
    2020 : Bare workflow introduced
         : EAS announced
         : Flexibility increases
    2022 : Development Builds launch
         : Custom native code without ejecting
         : EAS Build matures
    2024 : New Architecture support
         : Expo becomes RN's recommendation
         : Full native parity achieved
                

Expo has transformed from a limited sandbox to a complete development platform

The Old Complaints (Now Resolved)

What Changed?

The biggest shift was the introduction of Development Builds and the maturation of EAS Build. These two features eliminated the main pain points:

Feature Comparison

Let's do a detailed comparison across the dimensions that matter:

Development Experience

Native Capabilities

Build & Deployment

Cost Considerations

Development Builds: The Best of Both

Development Builds are the secret sauce that made Expo viable for production apps. They deserve special attention because they eliminate the historical trade-off between convenience and capability.

What is a Development Build?

Think of Expo Go as a "generic" app that can run any Expo project — but it can only include the native modules that Expo decided to bundle. A Development Build is a custom app built specifically for your project, including whatever native modules you need.

flowchart LR
    subgraph ExpoGo["Expo Go"]
        A["Pre-bundled
native modules"]
        B["Camera ✓"]
        C["Location ✓"]
        D["Notifications ✓"]
        E["Custom code ✗"]
    end
    
    subgraph DevBuild["Development Build"]
        F["Your native modules"]
        G["Camera ✓"]
        H["Location ✓"]
        I["Notifications ✓"]
        J["Custom code ✓"]
        K["Any library ✓"]
    end
    
    style ExpoGo fill:#fff3e0,stroke:#ff9800
    style DevBuild fill:#e8f5e9,stroke:#4caf50
                

Development Builds include exactly the native code your project needs

How It Works

1. Configure your project — Add the native modules you need to your project
2. Build once — Run eas build --profile development in the cloud
3. Install on device — Install the resulting app on your phone/simulator
4. Develop normally — The dev build connects to your Metro bundler, just like Expo Go
5. Rebuild when native code changes — Only needed when adding new native modules

When to Use What

flowchart TD
    A[Starting development] --> B{Need custom
native modules?}
    B -->|No| C[Use Expo Go]
    B -->|Yes| D[Create Development Build]
    
    C --> E{Adding a library that
requires native code?}
    E -->|No| C
    E -->|Yes| D
    
    D --> F[Develop with Dev Build]
    F --> G{Native dependencies
changed?}
    G -->|No| F
    G -->|Yes| H[Rebuild Development Build]
    H --> F
    
    style C fill:#fff3e0,stroke:#ff9800
    style D fill:#e8f5e9,stroke:#4caf50
    style F fill:#e8f5e9,stroke:#4caf50
                

Start with Expo Go, switch to Development Builds when you need custom native code

Common Native Module Scenarios

Making Your Decision

So when should you use Expo vs Bare React Native? Let's make this concrete:

Use Expo (Recommended) When:

Consider Bare React Native When:

Decision Flowchart

flowchart TD
    A[New React Native Project] --> B{Integrating into
existing native app?}
    B -->|Yes| C[Consider Bare RN
or Expo with care]
    B -->|No| D{Need on-premise builds
for compliance?}
    D -->|Yes| E[Bare RN with
custom CI]
    D -->|No| F{Want good DX and
faster development?}
    F -->|Yes| G["Use Expo ✓"]
    F -->|Neutral| G
    
    style G fill:#4caf50,stroke:#333,color:#fff
    style C fill:#ff9800,stroke:#333,color:#fff
    style E fill:#ff9800,stroke:#333,color:#fff
                

For most projects, Expo is the right choice

Can You Switch Later?

Summary

📚 Our Course Approach

Throughout this course, we'll use Expo with the following strategy:

1. Start with Expo Go — For quick setup and learning
2. Move to Development Builds — When we add features requiring native code
3. Use EAS Build — For production builds and deployment

This gives you the best of both worlds: fast iteration during learning, and production-ready skills for real apps.

🚀 What's Next?

Now that you understand why we're using Expo, let's get your development environment set up! In the next lesson, we'll install all the tools you need to start building.