We believe Expo tools are a great option for anyone looking to create amazing cross-platform apps quickly. Nonetheless, everyone's project is unique, and there may be reasons Expo is not the right choice for what you're building. Read on for some reasons why you may not want to use certain Expo tools with your project.
Similar to development builds, bare workflow also provides access to the underlying native projects and any native code. It's a "bare" native project where you can make direct changes to the project's native android/ and ios/ directories rather than continuously generating them on demand using the Expo config and prebuild.
EAS Build is compatible with bare workflow projects if you check in the native directories, but no longer runs prebuild, as that could overwrite any manual customizations you've made to the native project files. You'll have to configure the native directories on your own with native tools such as Android Studio or Xcode.
Expo Go provides a quick way to get started with your app development. It comes with a pre-configured set of libraries known as the Expo SDK. This makes development much faster and makes the mobile development experience much closer to the web development experience.
Like any other tool, it too has its own limitations:
Using a third-party library that requires native code
Using a third-party push notification service
We strongly recommend any projects that require additional libraries with native code to migrate to development builds. It's like creating a version of Expo Go that is specifically customized to your app's needs.