← Explore all skills

MOBILE DEVELOPMENT / expo

Expo Development Clients

Build a native-capable Expo development client for device and simulator testing.

“Build and distribute Expo development clients locally or via TestFlight for internal testing. For production TestFlight releases and store submission, use the eas-app-stores skill.”

01 / THE REASONING

Why this made the selection.

  • The source separates custom native dependencies from Expo Go use and distinguishes a development client from production store submission.
  • Test a custom native module or push-notification integration that Expo Go cannot host.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/expo/skills/expo-dev-client/SKILL.md
  • LICENSE
  • README.md

Our findings

  • The source separates custom native dependencies from Expo Go use and distinguishes a development client from production store submission.
  • The final feedback section invokes submit-expo-feedback@latest with npm confirmation suppressed, sending supplied actionable context to Expo; repeated failures route to a separate expo-skill-feedback skill.

Not established by this review

  • Third-party instructions and helpers were not executed; service access, host compatibility and outcomes remain untested.
  • Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx skills add expo/skills/plugins/expo/skills/expo-dev-client

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

npx skills add https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dev-client
  1. Install the pinned directory interactively and retain its referenced files; inspect the source before granting tool access.
  2. Choose local versus cloud and device versus simulator, configure the matching development profile, review signing and verify the exact artifact before installation.
  3. Before any feedback submission, obtain the user’s explicit approval, review the package and any separately loaded feedback skill, and remove secrets and private project details from the report.

Before you start

  • Expo project, expo-dev-client and platform build tools; EAS and developer accounts for cloud/distribution paths
  • Optional feedback needs npm/network access and a separately reviewed feedback package or skill.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dev-client/SKILL.md

    Supports: summary, review, install, access, limitations

  2. Pinned LICENSE ↗Checked

    https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/LICENSE

    Supports: license

  3. Pinned README.md ↗Checked

    https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md

    Supports: summary, review, install, access, limitations

  4. https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dev-client/SKILL.md

    Supports: upstreamDescription, review.notTested, review.reviewedAt

Evidence & Ask