expo-dev-client

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

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/NathanColosimo/kompose --skill expo-dev-client-nathancolosimo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/NathanColosimo/kompose/tree/main/.agents/skills/expo-dev-client
Command: npx skills add https://github.com/NathanColosimo/kompose --skill expo-dev-client-nathancolosimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create and distribute custom Expo development clients for testing native code changes, enabling closer iteration without relying solely on Expo Go.

Core Features & Use Cases

  • EAS Development Build: generate a development client that includes your custom native modules for testing on real devices.
  • Flexible Distribution: deploy to iOS via TestFlight and Android as dev builds for QA and branch testing.
  • Use Case: when adopting native modules or experimental native features, generate a dedicated client to validate changes across devices and environments.

Quick Start

Start by configuring an EAS development build and install the resulting development client on your 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 create an Expo development build for testing native code changes?

To create an Expo development build, configure an EAS development profile and build a dedicated dev client. This process includes your custom native modules and generates an installable client for testing on real devices.

When do I need a custom Expo dev client instead of Expo Go?

You need a custom Expo dev client when adopting native modules or experimental native features. It enables closer iteration and testing of custom native code changes across devices and environments without relying solely on Expo Go.

How do I distribute an EAS development build to iOS and Android for QA?

You can distribute EAS development builds flexibly by deploying to iOS via TestFlight and generating Android dev builds. This allows QA teams to test branch-specific native code changes across different environments.

Does EAS Build support configuring a development profile for custom native modules?

Yes, EAS Build supports development profile configuration and the developmentClient flag. This allows projects using custom native modules to generate, distribute, and install dedicated dev clients for validation.

What is the best way to test experimental native features in Expo across multiple devices?

The best way to test experimental native features is generating a dedicated Expo development client. By configuring an EAS development build, you validate changes across devices and environments using distributed builds.

Why use a dedicated dev client for branch testing in mobile apps?

A dedicated dev client allows you to validate custom native code changes on real devices. By distributing specific EAS development builds, QA can test branch implementations without Expo Go limitations.