dev-client

Automate Expo development client setup and distribution via eas.json and TestFlight.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Selfdb-io/StreamX --skill dev-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-client
Source: https://github.com/Selfdb-io/StreamX/tree/main/.agentone/skills/expo-app-design/skills/dev-client
Command: npx skills add https://github.com/Selfdb-io/StreamX --skill dev-client

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and distribution of Expo development clients for testing native code changes, eliminating the need for a full app store deployment during early development.

Core Features & Use Cases

  • Dev client creation: Bundle expo-dev-client for testing native code changes on real devices.
  • Platform coverage: Supports iOS and Android development workflows, including local builds and TestFlight distribution.
  • Use Case: When you need to test a custom native module or configuration changes, generate a development client and deploy it to a device for live testing.

Quick Start

Use this skill to configure a development build for your Expo app, then run the dev client on a real device or simulator and connect to your local Metro server.

Frequently Asked Questions about dev-client

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

FAQPage Schema
How do I test native code changes in an Expo app without a full app store deployment?

To test native code changes, you can create an Expo development client by bundling expo-dev-client. This generates a custom build that connects to your local Metro server, allowing live testing on real devices without app store deployment.

When do I need to create an Expo development client instead of using Expo Go?

You need an Expo development client when your project requires custom native modules or platform-specific configurations. Unlike Expo Go, a development client bundles your native dependencies, enabling direct testing on real devices or simulators.

How do I configure eas.json for building an Expo development client?

Configuring eas.json for an Expo development client involves setting the developmentClient property to true within your build profile. This ensures EAS Build generates a development client rather than a production binary.

Can I deploy an Expo development client to TestFlight for internal testing?

Yes, you can deploy an Expo development client to TestFlight. The workflow supports distributing your development build to TestFlight, allowing testers to install and verify native code changes on iOS devices.

Does this workflow support local builds for Expo development clients?

Yes, the workflow supports local builds for Expo development clients. You can generate builds locally to test native code changes directly on your connected physical device without relying on cloud build servers.

What is the best way to distribute a React Native development build to a physical device?

The best way to distribute a React Native development build is using an Expo dev client. You can install the generated binary directly onto a physical device to test native modules and connect to your local development server.