expo-dev-client

To test custom native modules unsupported by Expo Go, you create a custom Expo development client. This client acts like a custom version of Expo Go built specifically for your project to run and iterate on platform-specific native code changes.

You configure eas.json for an Expo development client by setting up a build profile with the development mode enabled. This involves enabling the developmentClient flag in your build profile to generate a build optimized for native code testing on physical devices.

Yes, you can distribute an Expo dev client via TestFlight for iOS device testing. The workflow supports building the development client with EAS Build and distributing it through TestFlight to test native code changes on physical Apple devices.

You need a development client instead of Expo Go when your React Native project requires custom native modules or platform-specific code. It allows engineers to iterate quickly on native features that the standard Expo Go application cannot render or execute.

The best way to build and install a dev client locally is using EAS Build to compile the development profile for Android and iOS. Once built, you can install the generated client directly onto your physical devices to test native code changes.