expo-dev-client

Build and distribute Expo development clients for testing native code changes.

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ravnhq/typescript-blueprint --skill expo-dev-client-ravnhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/ravnhq/typescript-blueprint/tree/main/.agents/skills/expo-dev-client
Command: npx skills add https://github.com/ravnhq/typescript-blueprint --skill expo-dev-client-ravnhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and ship Expo development clients to test native code changes on real devices or via TestFlight, reducing friction in the mobile iteration loop.

Core Features & Use Cases

  • Generate and distribute expo development clients for testing custom native modules
  • Use EAS Build to configure, build, and publish dev clients for iOS and Android
  • Validate workflows by testing builds on physical devices and sharing with QA teammates

Quick Start

Use EAS Build to create a development client and test it 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 custom native modules in React Native without Expo Go?

To test custom native modules outside Expo Go, you need to build and distribute an Expo development client. This custom client allows developers to iterate on native code changes and run device-based QA for iOS and Android workflows.

How do I distribute an Expo development client to TestFlight?

You can distribute an Expo development client to TestFlight by using EAS Build to configure and publish the build. This workflow reduces friction in the mobile iteration loop by allowing QA teammates to validate native code changes on physical devices.

When do I need a dev client instead of Expo Go for mobile development?

You need a dev client when your React Native project requires custom native modules beyond what Expo Go supports. Generating an Expo development client enables you to test these native code changes directly on real devices or via TestFlight.

Does EAS Build support configuring development profiles for iOS and Android?

Yes, EAS Build supports configuring development profiles for both iOS and Android. By setting the developmentClient flag, you can build and publish dev clients to test native code changes across mobile platforms.

What is the best way to share a React Native build with QA for device testing?

The best way to share a build with QA is to use EAS Build to generate an Expo development client. This allows teammates to test workflows on physical devices and validate native code changes efficiently.

Why does my Expo dev client build require the developmentClient flag?

The developmentClient flag is required because it satisfies configuration requirements for EAS Build development profiles. Setting this flag ensures the build is packaged correctly as a dev client for testing native code changes on devices.