Expo vs Bare React Native

Expo has evolved from a "managed" React Native wrapper to the officially recommended way to build React Native apps. The old distinction between "Expo" and "bare" has blurred significantly — Expo now supports custom native code via prebuild and config plugins.

The Modern Expo

Expo is no longer the limited managed environment it once was. With expo prebuild, Expo generates native iOS and Android projects that you can customize. Config plugins let you modify native code through JavaScript — adding permissions, native modules, and build settings without touching Xcode or Gradle directly.

Build and Deployment

Expo's EAS (Expo Application Services) provides cloud builds, OTA updates, and app store submission from the command line. You can build iOS apps without a Mac, run CI/CD without native toolchains, and push JavaScript updates to users instantly without app store review.

Bare React Native requires managing Xcode, Android Studio, signing certificates, and build infrastructure yourself. This gives maximum control but significantly increases DevOps complexity.

When to Go Bare

The primary reason to use bare React Native today is when you need a native library that is fundamentally incompatible with Expo's prebuild system (increasingly rare) or when your app has unusual native requirements that config plugins cannot address.

System Design Perspective

For system design interviews, the Expo vs bare question is an implementation detail. Focus on the mobile architecture: API design, offline support, push notifications, and caching strategies. The build tooling does not affect the system design.

Explore more in our comparison guides and interview questions.