expo-dev-client

Build and distribute Expo development clients for testing native code on devices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and install Expo development clients to test custom native code, platform-specific targets, and third-party native modules on physical devices without relying on the stock Expo Go app.

Core Features & Use Cases

  • Build development clients in the cloud or locally using EAS Build with a development profile that bundles expo-dev-client.
  • Submit iOS development client builds directly to TestFlight and install local builds on simulators or devices for testing.
  • Use Case: Test a feature branch that includes a native module or widget by producing a dev client, distributing it via TestFlight, and connecting it to your local Metro bundler.

Quick Start

Use the expo-dev-client skill to build and submit an iOS development client to TestFlight by running eas build -p ios --profile development --submit and then install the build on your device or TestFlight.

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 custom native modules in Expo on a physical device?▼

To test custom native modules in Expo, you build a custom development client using EAS Build. This replaces the stock Expo Go app, bundling your specific native code for local or cloud execution on physical devices.

When do I need an Expo development client instead of Expo Go?▼

You need an Expo development client when your project requires custom native modules, Apple targets, or third-party native libraries. Expo Go cannot run platform-specific native code, making a custom client necessary for these scenarios.

How do I submit an Expo iOS development build to TestFlight?▼

To submit an Expo iOS development build to TestFlight, run the EAS CLI command with a development profile and the submit flag. This requires proper signing credentials and an EAS configuration set to use a development client.

Do I need EAS CLI configuration to build an Expo development client?▼

Yes, EAS CLI configuration is required to build an Expo development client. You must define a development build profile with the setting developmentClient set to true to properly bundle the client for testing.

Can I build and test native code locally without Expo Go?▼

Yes, you can build and test native code locally using EAS Build with a development profile. This generates a custom development client that installs on simulators or devices and connects directly to your local Metro bundler.

What are the limitations of using Expo Go for testing native code?▼

Expo Go cannot test custom native code, platform-specific Apple targets, or third-party native libraries. You must create and distribute a custom Expo development client via EAS Build to bypass these limitations and run native code.