expo-dev-client

To build an Expo development client for custom native modules, you generate and compile the client locally or via cloud builds using EAS CLI, enabling physical device testing of native code changes.

Deploying an Expo app with native modules to TestFlight involves building a development client and submitting it through EAS. You can build and submit the iOS dev client in a single step using the 'eas build -p ios --profile development --submit' command.

Yes, building Expo development clients locally requires appropriate Xcode or Android development setup on your machine. The Skill integrates with EAS for building, but local builds rely on these native platform environments to compile the custom native code.

Yes, you can build iOS and Android Expo development clients independently. The Skill supports platform-specific builds, allowing you to target and compile native code for either operating system separately based on your testing requirements.

Yes, the Expo development client approach handles native code testing for widgets, app clips, and extensions. It generates clients specifically designed to integrate and test these custom native modules on physical devices.

You should use an Expo development client instead of Expo Go when your project includes custom native modules. Expo Go cannot test native code changes, whereas a development client compiles your specific native code for accurate physical device testing.