expo-dev-client

Build and distribute Expo development clients for iOS and Android devices.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/soham2008xyz/trade-tycoon --skill expo-dev-client-soham2008xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/soham2008xyz/trade-tycoon/tree/main/.agents/skills/expo-dev-client
Command: npx skills add https://github.com/soham2008xyz/trade-tycoon --skill expo-dev-client-soham2008xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of needing to validate native (platform-specific) changes on physical iOS or Android devices without relying on Expo Go.

Core Features & Use Cases

  • EAS development client creation: Build and distribute a development client that includes bundled native modules and your app’s branch changes.
  • TestFlight-based iOS testing: Produce an iOS development build and submit it directly to TestFlight for easy device testing.
  • Local dev-client workflow: Run your app with Metro bundler and connect through the installed dev client, enabling rapid iteration.

Quick Start

Use this workflow to build a development client and connect it to your local Metro bundler for immediate testing on a device.

Frequently Asked Questions about expo-dev-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test React Native native modules on a physical device?

To test React Native native modules on a physical device, build an Expo development client using EAS Build. This client bundles your local native code changes, replacing Expo Go to validate platform-specific behavior directly on iOS and Android hardware.

Can I submit an iOS development client directly to TestFlight?

Yes, you can submit an iOS development client directly to TestFlight. The workflow builds your custom Expo development client and submits it to TestFlight, enabling easy distribution and testing of native changes on physical Apple devices.

Do I need an EAS development profile to build a custom Expo client?

Yes, building a custom Expo development client requires an EAS development profile with the developmentClient setting enabled. This profile configures the necessary credentials and build environment to compile your native modules for physical device testing.

How do I connect an installed Expo dev client to the Metro bundler?

To connect an installed Expo dev client to the Metro bundler, run your local Metro bundler server and open the development client on your device. The app connects to the bundler, enabling rapid iteration without rebuilding the native binary.

Why should I use a development client instead of Expo Go?

Use a development client instead of Expo Go when validating custom native modules or Apple-target features. Expo Go lacks bundled native code changes, whereas a custom dev client includes your branch modifications for accurate physical device testing.