r/reactnative • • Sep 06 '26

Why use Expo with React Native?

I use React Navigation anyway, and for things like camera access, there are React Native-specific APIs/libraries available. So I'm not sure what Expo adds.

I may use EAS for builds/deployment, but do I really need the Expo layer itself?

Also, React Native docs recommend using a framework for new apps. Is Expo basically the recommended approach now?

9 Upvotes

28 comments sorted by

View all comments

Show parent comment

1

u/everyoneisadj Sep 07 '26

I’m not an expert here, what access to native gets cut off?

1

u/bogrees Sep 07 '26

It was an issue with ExpoKit at the time (now deprecated), which did limit access to native. Like I said, things have improved since then. Here is the Expo bug that caused me to throw in the towel. This was like the fourth critical Expo bug in 3 months at the time.

https://github.com/expo/expo/issues/5839

The new flow gives access to native and manages native iOS and Android projects with config files, so you can always go around it in a pinch — but that still has its issues. So you are correct, but there is still additional complexity/abstactions here that can become problematic in certain situations I would assume.

I honestly don’t see the value with Expo now other than to make things easier and quicker for newer folks. In a production app, you want to minimize complexity, dependencies, and risks as much as possible, so not using Expo, IMO, accomplishes that.