expo-dev-client
Skill8 starsChanged 3 months agoMITView on GitHub
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- elbionredenica/consumer-app-startertheir own version, first seen Nov 8, 2026
- nnawar706/fluentotheir own version, first seen Nov 8, 2026
- dalonga-kohi/mawltheir own version, first seen Nov 8, 2026
- deonmenezes/mobile-app-skilltheir own version, first seen Nov 1, 2026
- Ultimate-Alchemy/claude-skillstheir own version, first seen Oct 15, 2026
- mahik504/orchestra-workflowtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use expo-native-ui, eas-update-insights and 6 more.
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.
wpankSkillexpo-native-ui
Build beautiful native iOS/Android apps with Expo Router. Covers route structure, native tabs, animations, blur effects, liquid glass, SF Symbols, and platform patterns.
Also in 4 projects that use this
nnawar706Skilleas-update-insights
Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.
Also in 3 projects that use this
deonmenezesSkillexpo-upgrade
Guidelines for upgrading Expo SDK versions and fixing dependency issues
Also in 3 projects that use this
arcboxlabsSkillexpo-project-structure
Framework (OSS). Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.
Also in 4 projects that use this
CaiZongyuanSkillexpo-ui
This skill should be used when users need to work with Expo UI (@expo/ui) for integrating SwiftUI components into React Native applications. It provides comprehensive guidance on installation, Host component, SwiftUI primitives, layouts, modifiers, native tabs navigation, and v10 preview features.
Also in 3 projects that use this
tradernetworkSkilleas-app-stores
Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- openai/plugins★ 7.8ksame name
- CherryHQ/cherry-studio-app★ 4.1ksame name
- kingstinct/react-native-healthkit★ 719same name
- Talljack/echo-type★ 303same name
- ruizrica/agent-pi★ 274same name
- arcboxlabs/linkcode★ 147same name
- robinebers/skills★ 48same name
- PIXARTSeu/Synapse★ 9same name
- xfstudio/skills★ 9same name
- deonmenezes/mobile-app-skill★ 4same name
7 more not listed
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 repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 150
If the Dev Client build and the production build are on different runtimeVersions, OTA won't apply.
“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
expo-dev-client
Setting up custom development builds with expo-dev-client. Comparison with Expo Go, build profiles, a custom dev menu, runtime-version compatibility, and the EAS Update test flow.
What It Does
expo-dev-clientsetup + build profile- Expo Go vs Dev Client decision
- Dev menu (cmd+D / shake) and custom actions
- Dev launcher (multi-app, multi-server)
- EAS Update test flow (via the dev client)
- Runtime version & native dep compatibility
Setup
npx expo install expo-dev-clientapp.json (automatic plugin):
{
"expo": {
"plugins": ["expo-dev-client"]
}
}EAS profile:
{
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"ios": { "simulator": true },
"channel": "development"
}
}
}Build:
eas build --profile development --platform ios
eas build --profile development --platform android
# or local
npx expo run:ios
npx expo run:androidExpo Go vs Dev Client
| Feature | Expo Go | Dev Client |
| Setup | From the App Store | Your own build |
| Native module | Only Expo SDK | All custom modules |
| Config plugin | Limited | Full support |
| Bundle ID | host.exp.Exponent | Your own ID |
| Splash/icon | Generic | Your own |
| EAS Update | ❌ | ✅ |
| Push notification | Limited | Full support |
| Production-like | No | Yes |
In modern Expo the default recommendation is Dev Client. Expo Go is for quick prototyping only.
Start the Dev Server
npx expo start --dev-client
# or
npx expo start
# → the "dev client" option appears in the QR menuOnce the Dev Client app opens:
- Show the server URL (LAN/Tunnel)
- Scan the QR or enter the URL manually
- The bundle loads
Dev Launcher
With the Dev Client's Switch to another bundle:
- Connect to a different dev server (collab)
- Preview an EAS Update branch
- Preview the production bundle (rare)
Dev Menu
Trigger:
- iOS sim:
Cmd+DorCmd+Ctrl+Z - Android emulator:
Cmd+M/Ctrl+M - Device: shake
Menu contents:
- Reload
- Toggle Element Inspector
- Toggle Performance Monitor
- Open JS Debugger (Hermes inspector)
- Show Dev Menu (custom button)
Custom Dev Menu Item
import { registerDevMenuItems } from "expo-dev-menu";
if (__DEV__) {
registerDevMenuItems([
{
name: "Reset Storage",
callback: async () => {
await AsyncStorage.clear();
},
},
{
name: "Open Sentry",
callback: () => Linking.openURL("https://sentry.io/myorg/myapp"),
},
]);
}EAS Update Test Flow
Previewing an EAS Update branch in the Dev Client:
- Publish an update to the branch
eas update --branch preview --message "test" - In the Dev Client app go to Extensions > Updates
- Select the branch, open it as a preview
- Return to normal mode after testing
Runtime Version Compatibility
If the Dev Client build and the production build are on different runtimeVersions, OTA won't apply. During testing:
{
"expo": {
"runtimeVersion": { "policy": "fingerprint" }
}
}The moment you add a native dep to the dev client, a new build is required. JS-only changes already arrive over the dev server.
Debug Build vs Production Build
| Type | Hermes | JS bundle | Splash | Dev menu |
| Debug (dev client) | Dev | Metro server | Native | Yes |
| Release (preview) | Prod | Embedded | Native | No |
| Production | Prod | Embedded | Native | No |
Best Practices
- Dev client a separate build per team member (Apple device UDIDs registered)
- Tunnel usage:
npx expo start --tunnel(behind a firewall) developmentClient: trueprofile for the dev profile only- Hermes turned on in dev too (same behavior as production)
- AndroidManifest cleartext traffic is needed in dev; turn it off in production
Common Failure Patterns
- Device can't find the dev server → not on the same LAN, or a firewall
- "Native module XYZ doesn't exist" → the dev client was not rebuilt
- iOS simulator dev client crash →
simulator: truemissing in the profile - Old client after a bundle ID change → uninstall + reinstall
- Tunnel is too slow → prefer LAN or
--lan
Hard Refusal
- Distributing a production bundle via the dev client without signing
- Registering a device UDID without the owner's permission
- Leaving the dev menu open in production (security risk)
Output Format
- Build profile (
development) expo-dev-clientinstall command- Start command (copy-paste)
- Why dev client instead of Expo Go? (rationale)
- EAS Update test plan
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.

