expo-dev-client

Build Expo development clients for iOS and Android with EAS profiles.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/atemaguer/bfloat-ide --skill expo-dev-client-atemaguer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/atemaguer/bfloat-ide/tree/main/resources/skills/expo-dev-client
Command: npx skills add https://github.com/atemaguer/bfloat-ide --skill expo-dev-client-atemaguer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create and distribute custom Expo development clients when your app needs native code or device-specific testing beyond Expo Go.

Core Features & Use Cases

  • Dev-client decision support: Tells you when a development client is actually necessary and when Expo Go is enough.
  • EAS build setup: Guides development profile configuration for local builds, cloud builds, and submission workflows.
  • Platform testing workflow: Covers iOS, Android, simulator installation, physical device installs, and TestFlight distribution for native app validation.
  • Use Case: A team adding a local Expo module can use this Skill to build a signed development client, install it on a device, and connect it to the Metro bundler for testing.

Quick Start

Ask the skill to prepare a development client workflow for your Expo app, specifying whether you need local testing, TestFlight, or a platform-specific iOS or Android build.

Frequently Asked Questions about expo-dev-client

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

FAQPage Schema
When do I need a custom Expo development client instead of Expo Go?

You need a custom Expo development client when your app requires custom native code or device-specific testing that exceeds the capabilities and native modules supported by Expo Go.

How do I configure EAS build profiles for an Expo dev client?

Configure EAS development profiles by enabling the developmentClient option, setting autoIncrement versioning, and configuring the remote app version source settings for your iOS or Android builds.

Can I distribute an Expo development client through TestFlight?

Yes, you can distribute an Expo development client through TestFlight by configuring the EAS submission workflow for iOS to validate native app behavior on physical devices.

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

After installing the signed development client on a physical device or simulator, launch the app and connect it to the local Metro bundler to test your local Expo modules.

Does this workflow support local EAS builds for both iOS and Android?

Yes, the workflow supports local EAS builds alongside cloud builds, covering simulator installation and physical device deployment for both iOS and Android platforms.

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

Expo Go limits testing because it cannot load custom native code or local Expo modules, requiring a dedicated development client build to validate device-specific functionality.