expo-dev-client

The expo-dev-client skill provides comprehensive guidance for developers who need to extend Expo apps with custom native code. While most Expo projects function perfectly within the standard Expo Go environment, specific requirements—such as integrating custom native modules, supporting Apple targets like widgets, App Clips, or app extensions, and utilizing third-party native libraries—necessitate the use of a development client. This skill serves as an interface for managing the lifecycle of these clients, ensuring developers can iterate on native code effectively.

• Streamline EAS Build configuration by defining specific development profiles within eas.json, including automatic versioning and build targeting.

• Automate the build-to-distribution pipeline by integrating direct submission to TestFlight, allowing for rapid deployment and device-side testing.

• Facilitate local development builds using the EAS CLI, providing commands for iOS and Android, including local debugging and simulator/emulator installation.

• Manage connection lifecycle between local Metro bundlers and development client instances via QR code scanning or manual URL entry for live reloading of native-enriched apps.

• Troubleshoot complex build scenarios such as signing errors, build cache management, and version compatibility checks.

• Intended for React Native developers working with custom native code or non-standard Expo modules.

• Prerequisite: Requires an EAS account and basic knowledge of the Expo CLI toolchain.

• Inputs typically include terminal commands for eas build, configuration files like eas.json, and native project settings.

• Outputs comprise signed .ipa, .apk, or .aab files, TestFlight build notifications, and a functional development environment linked to the local Metro server.

• Constraints: Development clients increase build complexity and overhead compared to Expo Go; use this skill only when your app requirements exceed the standard capabilities of Expo Go.