[chainwax]

My company is moving our app to React Native and evaluated Expo as an option. Our conclusion was that we needed some of the features that using Expo doesn't let you use (a lot of native modules, as we're not rewriting 100% of the app all at once).

Additionally, I think RN has come a really long way from where it was when Expo first came about. Expo sought to smooth over a lot of rough edges, some of which no longer exist.

I think Expo realizes this as well, as their main revenue generator is now their deployment tools. The framework is opinionated toward using those paid services, which my org doesn't want to use as we already have processes for building and deploying, which makes working with it cumbersome.

https://expo.dev/pricing

[jameside]

Expo supports custom native code including your existing modules. It is a much smaller step to start using Expo if you are already using React Native.

Using Expo without EAS, the paid services, is definitely supported. The Expo framework is free and open source and is designed to be generally decoupled from EAS. "npx expo prebuild:{android,ios}" will generate "android" and "ios" directories that can be built with existing build processes.

Expo: free and open source framework. Includes Expo CLI, Expo Modules, Config Plugins, Expo Router, debugging tools. EAS: hosted paid services. Includes builds, submissions, updates, credentials. Works with any React Native project whether or not it is using Expo.