expo-dev-client
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
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.
17 other projects use a version of this, 16 of them edited.
Adopted by
Most recently taken up by
- fatihkan/baditheir own version, first seen Nov 16, 2026
- elbionredenica/consumer-app-starteredited, first seen Nov 8, 2026
- nnawar706/fluentoedited, first seen Nov 8, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- Ultimate-Alchemy/claude-skillsedited, first seen Oct 15, 2026
- mahik504/orchestra-workflowedited, first seen Oct 15, 2026
Used with
Projects with it also use react-native-best-practices.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
pyinxSkillreact-native-best-practices
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 16
- openai/plugins★ 7.8k88% same
- CherryHQ/cherry-studio-app★ 4.1k88% same
- kingstinct/react-native-healthkit★ 71988% same
- Talljack/echo-type★ 30388% same
- ruizrica/agent-pi★ 27488% same
- arcboxlabs/linkcode★ 14797% same
- robinebers/skills★ 4888% same
- PIXARTSeu/Synapse★ 988% same
- xfstudio/skills★ 988% same
- deonmenezes/mobile-app-skill★ 493% same
6 more not listed
Wrote their own version · 1
- fatihkan/badi★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- cavemanSkill
- eas-app-storesSkill
- eas-hostingSkill
- eas-observeSkill
- eas-simulatorSkill
- eas-update-insightsSkill
- eas-updateSkill
- eas-workflowsSkill
- expo-animationSkill
- expo-app-clipSkill
- expo-brownfieldSkill
- expo-data-fetchingSkill
- expo-design-systemSkill
- expo-domSkill
- expo-examplesSkill
- expo-moduleSkill
- expo-native-uiSkill
- expo-overviewSkill
- expo-project-structureSkill
- expo-routerSkill
- expo-uiSkill
- expo-upgradeSkill
- expo-web-to-nativeSkill
- frontend-designSkill
- ios-designSkill
- ui-ux-pro-maxSkill
The file
We split this skill into the rules it gives an agent
6 rules. 2 are common, 2 are distinctive, and 2 are very specific to this project.
2
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Use EAS Build to create development clients for testing native code changes on physical devices.
- Very specific: line 25
Ensure eas.json has a development profile:
- Common: line 69
After receiving the TestFlight email:
- Distinctive: line 179
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
- Distinctive: line 183
Only submit when you have something specific and actionable to report.
- Very specific: line 184
If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went …
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.
Free locally; cloud builds are paid.
expo-dev-clientitself is open source and building locally is free. Building or distributing via EAS Build/TestFlight uses your EAS plan's build minutes and needs a paid Apple Developer account for device/TestFlight distribution. See https://expo.dev/pricing.
Important: When Development Clients Are Needed
Development clients are the recommended setup for any real or production app. Expo Go is a playground for learning and quick experiments with the native libraries it bundles; most apps outgrow it and move to a development client. See Expo Go vs. development builds for the full reasoning.
You need a dev client ONLY when using:
- Local Expo modules (custom native code)
- Apple targets (widgets, app clips, extensions)
- Third-party native modules not in Expo Go
- Config plugins, or testing remote push notifications and App/Universal Links
EAS Configuration
Ensure eas.json has a development profile:
{
"cli": {
"version": ">= 16.0.1",
"appVersionSource": "remote"
},
"build": {
"production": {
"autoIncrement": true
},
"development": {
"autoIncrement": true,
"developmentClient": true
}
},
"submit": {
"production": {},
"development": {}
}
}Key settings:
developmentClient: true- Bundles expo-dev-client for development buildsautoIncrement: true- Automatically increments build numbersappVersionSource: "remote"- Uses EAS as the source of truth for version numbers
Building for TestFlight
Build iOS dev client and submit to TestFlight in one command:
eas build -p ios --profile development --submitThis will:
- Build the development client in the cloud
- Automatically submit to App Store Connect
- Send you an email when the build is ready in TestFlight
After receiving the TestFlight email:
- Download the build from TestFlight on your device
- Launch the app to see the expo-dev-client UI
- Connect to your local Metro bundler or scan a QR code
Building Locally
Build a development client on your machine:
# iOS (requires Xcode)
eas build -p ios --profile development --local
# Android
eas build -p android --profile development --localLocal builds output:
- iOS:
.ipafile - Android:
.apkor.aabfile
Installing Local Builds
Install iOS build on simulator:
# Find the .app in the .tar.gz output
tar -xzf build-*.tar.gz
xcrun simctl install booted ./path/to/App.appInstall iOS build on device (requires signing):
# Use Xcode Devices window or ideviceinstaller
ideviceinstaller -i build.ipaInstall Android build:
adb install build.apkBuilding for Specific Platform
# iOS only
eas build -p ios --profile development
# Android only
eas build -p android --profile development
# Both platforms
eas build --profile developmentChecking Build Status
# List recent builds
eas build:list
# View build details
eas build:viewUsing the Dev Client
Once installed, the dev client provides:
- Development server connection - Enter your Metro bundler URL or scan QR
- Build information - View native build details
- Launcher UI - Switch between development servers
Connect to local development:
# Start Metro bundler
npx expo start --dev-client
# Scan QR code with dev client or enter URL manuallyWhen you launch the dev client yourself to screenshot or drive it, skip the onboarding sheet, the dev menu at launch, and the Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell; for a URL you open yourself, use <scheme>://?__expo_url=<encoded dev server URL>&__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1. On SDK 57 and earlier, launch the iOS app with the -EXDevMenu* launch arguments, and on Android open <scheme>://expo-development-client/?url=<encoded dev server URL>&disableOnboarding=1&disableFab=1&disableAutoLaunch=1. See ../expo-overview/references/launch-without-dev-menu.md for the exact commands.
Troubleshooting
Build fails with signing errors:
eas credentialsClear build cache:
eas build -p ios --profile development --clear-cacheCheck EAS CLI version:
eas --version
eas updateSubmitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-dev-client" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using --category evals and the relevant Expo package or command as --subject.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

