expo-dev-client

To test custom native modules without Expo Go, you can build an Expo development client. This creates a customized runtime for iOS and Android devices that supports native code changes, widgets, and app clips in a controlled environment.

An Expo dev client is a customized version of your React Native app for testing native code changes on real devices. You need it when your project includes custom native modules, widgets, or app clips that the standard Expo Go app cannot run.

To configure EAS for an Expo dev client, you modify the eas.json file to enable the developmentClient option in your build profiles. This allows you to build and distribute the client for local testing or TestFlight.

Yes, you can distribute an Expo development client to testers via TestFlight. By configuring your EAS build profiles, you can generate builds suitable for app store distribution and share them with stakeholders for testing on iOS devices.

Yes, building an Expo dev client works for both iOS and Android local builds. The configuration supports creating development clients to test native changes across both platforms directly on real devices.

You should use a custom dev client instead of Expo Go when your mobile testing requires validating native modules, widgets, or app clips. Expo Go has limitations with custom native code, whereas a dev client provides a controlled environment for these specific native workflows.