Expo vs bare React Native

Introduction

Expo and bare React Native are two ways to build mobile apps with React Native. Knowing the difference helps you pick the best tool for your app.

You want to quickly build and test an app without installing many tools.

You need to use native device features easily without writing native code.

You want full control over native code and custom native modules.

You plan to add advanced native features not supported by Expo.

You want to publish your app with custom native configurations.

Syntax

React Native

Expo: Uses managed workflow with pre-built tools and libraries.
Bare React Native: Uses plain React Native setup with full native code access.

Expo simplifies setup and development with many built-in features.

Bare React Native requires more setup but offers full native customization.

Examples

Start a new Expo app quickly with one command.

React Native

expo init MyApp
cd MyApp
expo start

Create a bare React Native app with full native code access.

React Native

npx react-native init MyApp
cd MyApp
npx react-native run-ios

Sample App

This simple app works the same in both Expo and bare React Native. It shows text and a button that shows an alert when pressed.

React Native

import React from 'react';
import { Text, View, Button, Alert } from 'react-native';

export default function App() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Hello from React Native!</Text>
      <Button title="Press me" onPress={() => Alert.alert('Button pressed!')} />
    </View>
  );
}

Important Notes

Expo is great for beginners and fast prototyping.

Bare React Native is better for apps needing custom native code.

You can start with Expo and later eject to bare React Native if needed.

Summary

Expo offers easy setup and many built-in tools.

Bare React Native gives full control over native code.

Choose based on your app needs and experience level.

Practice

1. Which statement best describes Expo in React Native development?

easy

A. Expo provides an easy setup with many built-in tools and services.

B. Expo requires manual linking of native modules for every feature.

C. Expo does not support running apps on physical devices.

D. Expo is only for web development, not mobile apps.

Solution

1. Step 1: Understand Expo's purpose

   Expo is designed to simplify React Native development by providing many built-in tools and services out of the box.

2. Step 2: Compare with other options

   Unlike bare React Native, Expo does not require manual linking of native modules and supports running apps on physical devices easily.

3. Final Answer:

   Expo provides an easy setup with many built-in tools and services. -> Option A

4. Quick Check:

   Expo = Easy setup and built-in tools [OK]

Hint: Expo means easy start with many tools included [OK]

Common Mistakes:

• Thinking Expo requires manual native code linking
• Believing Expo can't run on real devices
• Confusing Expo with web-only frameworks

2. Which of the following is the correct way to start a new Expo project?

easy

A. npx react-native init MyApp

B. react-native run-ios

C. npm create-react-app MyApp

D. expo init MyApp

Solution

1. Step 1: Identify Expo project creation command

   The command expo init MyApp is used to create a new Expo project with templates and setup.

2. Step 2: Differentiate from bare React Native commands

   npx react-native init is for bare React Native, not Expo. Other options are unrelated or for web.

3. Final Answer:

   expo init MyApp -> Option D

4. Quick Check:

   Expo project start = expo init [OK]

Hint: Expo projects start with 'expo init' command [OK]

Common Mistakes:

• Using 'npx react-native init' for Expo projects
• Confusing React web commands with React Native
• Trying to run iOS build command before project creation

3. What will happen if you try to use a native module not supported by Expo in an Expo managed project?

medium

A. The app will build and run without errors.

B. You will get a build error or runtime crash.

C. Expo automatically adds support for all native modules.

D. The app will silently ignore the native module.

Solution

1. Step 1: Understand Expo's native module support

   Expo supports many native modules but not all. Unsupported modules cause build or runtime errors.

2. Step 2: Predict behavior when using unsupported modules

   Since Expo does not allow custom native code in managed workflow, using unsupported native modules leads to errors.

3. Final Answer:

   You will get a build error or runtime crash. -> Option B

4. Quick Check:

   Unsupported native module in Expo = error [OK]

Hint: Unsupported native modules cause errors in Expo [OK]

Common Mistakes:

• Assuming Expo adds all native modules automatically
• Thinking unsupported modules are ignored silently
• Believing Expo supports all bare React Native features

4. You have a React Native app created with Expo but need to add custom native code. What is the best way to fix this?

medium

A. Eject the Expo project to bare React Native workflow.

B. Keep using Expo and add native code directly.

C. Rewrite the app using React web instead.

D. Use Expo's managed workflow without changes.

Solution

1. Step 1: Identify the limitation of Expo managed workflow

   Expo managed workflow does not allow adding custom native code directly.

2. Step 2: Choose the correct approach to add native code

   Ejecting the Expo project converts it to bare React Native, allowing full native code access.

3. Final Answer:

   Eject the Expo project to bare React Native workflow. -> Option A

4. Quick Check:

   Need native code? Eject Expo [OK]

Hint: Eject Expo to add custom native code [OK]

Common Mistakes:

• Trying to add native code in Expo managed workflow
• Ignoring the need to eject before native code
• Switching to React web instead of native

5. You want to build a complex app with custom native modules and full control over build tools. Which approach is best?

hard

A. Build a web app instead of a mobile app.

B. Use Expo managed workflow for faster development.

C. Start with bare React Native to access native code freely.

D. Use Expo and avoid any native code.

Solution

1. Step 1: Analyze app requirements

   The app needs custom native modules and full control over build tools, which Expo managed workflow limits.

2. Step 2: Choose the suitable React Native approach

   Bare React Native allows direct native code access and full control over build configurations, fitting the requirements.

3. Final Answer:

   Start with bare React Native to access native code freely. -> Option C

4. Quick Check:

   Custom native + control = bare React Native [OK]

Hint: Complex native needs? Choose bare React Native [OK]

Common Mistakes:

• Choosing Expo for apps needing custom native code
• Confusing web apps with native mobile apps
• Avoiding bare React Native despite native needs