hjemmesidekongen/expo-dev-client

expo-dev-client

expo-dev-client replaces Expo Go with a custom native runtime that includes your app's native modules and config plugin modifications. Required as soon as you add any package with a native layer.

Dev Client vs Expo Go

Expo Go: sandboxed, zero-build, Expo SDK modules only. No third-party native modules, no custom native code. Start here. Dev Client: a real development build of your app — includes your native dependencies, config plugin results, and custom native code. Requires a one-time build per native change; JS changes reload instantly without rebuilding.

Switch from Expo Go to dev client the moment you need a native module.

Setup

npx expo install expo-dev-client
npx expo start --dev-client   # after building and installing the dev client app

EAS Build development profile:

{ "build": { "development": { "developmentClient": true, "distribution": "internal",
    "ios": { "simulator": true }, "android": { "buildType": "apk" } } } }

Build: eas build --profile development --platform ios|android

Prebuild Workflow

Native directories are managed by expo prebuild — never edit android/ or ios/ by hand. Apply all native customizations through config plugins in app.config.js. Run npx expo prebuild --clean to regenerate.

Debugging Tools

• React DevTools: j in Metro terminal or shake device
• Flipper: add react-native-flipper; Network, Layout, and DB plugins work in dev client builds
• Xcode / Android Studio: full native debuggers, instruments, logcat, memory profiler
• Network: Proxyman or Flipper Network plugin with SSL proxying

See references/process.md for native module integration, config plugin authoring, team distribution via EAS, error handling patterns, and anti-patterns.