What problem does it solve?
It solves the problem of slow or unreliable testing of custom native code changes in Expo apps by letting you run a development client on physical devices and simulators.
Core Features & Use Cases
- EAS development-client builds: Create dev clients configured to include expo-dev-client so your app can load native changes that go beyond what Expo Go supports.
- TestFlight and local build workflows: Build for iOS via EAS and submit to TestFlight, or generate local installable artifacts for both iOS and Android.
- Metro bundler integration: Connect the installed dev client to your local Metro bundler using a URL or QR code for fast iteration during development.
Use Case: You’re working on an app branch that uses Apple targets (widgets/app clips/extensions) or a local/native module, and you need real-device testing to verify native behavior before production release.
Quick Start
Ask: "Build an Expo development client for my iOS app using the development profile and submit it to TestFlight with EAS."