expo-dev-client
Expo Dev Client
Overview
A custom development client is a debug build of your app that includes your specific native modules and configuration. It replaces Expo Go when you need native code that Expo Go does not bundle.
Core principle: Use Expo Go for rapid prototyping. Switch to a dev client when you need custom native code, and use EAS Build to create and distribute it.
When to Use
Use a dev client when your app requires:
- Custom native modules not included in Expo Go (e.g., Bluetooth, NFC, custom camera pipelines)
- Apple ecosystem integration (HealthKit, HomeKit, CarPlay, App Clips)
- Third-party native SDKs (Stripe native, Mapbox, Firebase Analytics with custom config)
- Custom native configuration (specific entitlements, background modes, custom URL schemes)
- Config plugins that modify native project files
- Expo Modules API for writing your own native modules
More from bidah/react-native-hifi
use-dom
Use when embedding web-only libraries or DOM content in React Native apps, including charts with recharts, syntax highlighting, rich text editors, or any component that requires a browser DOM
1software-mansion-best-practices
Software Mansion's best practices for production React Native apps on the New Architecture. Use when writing, reviewing, or debugging React Native code across animations, gestures, SVG, haptics, on-device AI, multimedia, rich text, multithreading, or audio. Trigger on any React Native implementation question or when a more specific sub-skill below matches the task.
1writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
1agent-device
Automates interactions for iOS simulators/devices and Android emulators/devices. Use when navigating apps, taking snapshots/screenshots, tapping, typing, scrolling, or extracting UI info on mobile targets.
1expo-ui-swift-ui
Use when building iOS-specific UI components using SwiftUI views in Expo, embedding React Native views in SwiftUI with RNHostView, or implementing native iOS interfaces beyond cross-platform components
1brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
1