expo-dev-client

To test native code changes on a physical device, build a custom Expo development client. This creates a tailored native app for iOS or Android, allowing you to validate native modules directly on real hardware.

You need a custom Expo dev client when testing native code modifications beyond standard Expo Go functionality. It enables full native support for custom modules, ensuring advanced features work correctly before production release.

The best way to build and distribute a custom Expo development client is using EAS CLI. It facilitates configuration and deployment workflows, allowing you to distribute via TestFlight or locally for thorough native testing.

Yes, you can use EAS CLI to deploy a custom Expo dev client to both iOS and Android. It supports the build and deployment workflows needed to install tailored native apps onto physical devices for testing.

Building a custom Expo dev client fully supports testing native modules on both iOS and Android. It creates tailored native apps to validate custom native code modifications across physical devices before production release.

You should build a custom Expo development client when customizing native modules in an Expo app. It is required when you need to test native code changes on a real device with full native support, bypassing Expo Go limitations.