Why Expo Changed the Way I Build Mobile Apps

I've been building mobile apps for over a decade. For most of that time, mobile development meant one thing: pain. Two codebases, two languages, two deployment pipelines, and a machine so buried under Xcode and Android Studio that a fresh git clone felt like a small miracle.

React Native was a step forward — one language, two platforms. But the native toolchain was still there, lurking. Gradle builds that failed for reasons buried three stack frames deep in Java. CocoaPods dependency hell. A simulator that refused to launch until you restarted the Mac.

Then I started using Expo seriously, and a lot of that pain simply disappeared.

What Expo Actually Is

Expo is not a framework on top of React Native. It's closer to a managed platform — a set of tools, services, and conventions that handle the parts of mobile development that have nothing to do with your actual product.

The distinction matters. When I'm building Barba Studio, I want to think about booking flows and barber schedules, not provisioning profiles and push notification entitlements. Expo lets me do that.

OTA Updates: Shipping Without the App Store

This is the feature that changes everything in production.

With a standard React Native app, every update goes through app store review. Bug fix? Submit, wait, hope. With Expo's OTA (over-the-air) updates — now part of EAS Update — you push a JavaScript bundle directly to users' devices. No review. No waiting. Users get the fix the next time they open the app.

The limitation is real: you can't ship native code changes this way. But the majority of updates — UI fixes, logic changes, copy tweaks — are pure JavaScript. OTA handles all of them instantly.

For a solo developer running a live product, this is the difference between a bug lasting three days and a bug lasting three minutes.

EAS Build: The Cloud Build That Actually Works

Before EAS Build, building a release binary meant having the right version of Xcode on the right version of macOS, with the right certificates in the right keychain, with the right provisioning profiles, all aligned on the right day of the week.

EAS Build moves that entire process to the cloud. You run eas build, you wait, you get a binary. Your local machine doesn't need Xcode. It doesn't need Android Studio. It doesn't need any of it.

This sounds minor until you've lost an afternoon to a code signing error that turned out to be a stale certificate. After that, cloud builds feel like a gift.

EAS Submit: One Command to Both Stores

Once you have a binary, eas submit uploads it to the App Store and Google Play. Credentials are stored in EAS's servers — no more juggling API keys in local environment files or praying that the CI machine has the right Google Play JSON file mounted somewhere.

The full pipeline — code → build → submit — runs in a single session without touching a GUI.

The Development Experience

Day-to-day development with Expo is fast in a way that's hard to describe until you've felt it. Expo Go lets you open your app on a real device by scanning a QR code. Changes in code reflect instantly via hot reload. No build step. No cable. No simulator quirks.

For complex apps that need custom native modules, there's the development build — a custom version of Expo Go built for your specific project. You build it once, run it on device, and from that point the inner development loop is identical: fast, hot, no friction.

What You Give Up

Expo is not for every app. If your product requires deep native customisation — custom camera pipelines, Bluetooth peripherals, tight system integrations — the managed workflow will eventually get in your way.

But that's a narrow category. Most apps — booking systems, social features, dashboards, e-commerce flows — never need to leave the managed layer. And for those apps, the tradeoff is straightforward: you give up some low-level control in exchange for dramatically faster development and a much smaller surface area of things that can go wrong.

I'll take that trade every time.

Twelve Years Later

I shipped my first mobile app in 2013. Java. Android SDK. An emulator that took four minutes to boot and crashed on arrival. I've watched the ecosystem evolve through Swift, through the first React Native betas, through the slow maturation of the toolchain.

Expo is the best the mobile development experience has ever been. Not perfect — nothing is — but genuinely good. For a solo developer building real products for real users, "genuinely good" is more than enough.

If you're building a new React Native app and you're not starting with Expo, I'd ask why. The escape hatch is always there if you need it. The productivity you give up while waiting to need it is not coming back.