What problem does it solve? Adding React Native to an existing native iOS or Android app requires choosing between shipping a prebuilt AAR/XCFramework or embedding React Native sources directly into Gradle and CocoaPods builds, and each path involves intricate configuration that is easy to get wrong. ## Core Features & Use Cases - Isolated approach: Build React Native as a prebuilt AAR or XCFramework (or Swift Package) with expo-brownfield, so native teams consume it as a regular dependency without Node or RN tooling. - Integrated approach: Add React Native and Expo directly to existing Gradle and CocoaPods builds with autolinking, hot reload, and a unified build pipeline. - Decision guidance and troubleshooting: A comparison reference maps team structures and constraints to the right approach, and a troubleshooting guide covers Metro connectivity, XCFramework signing, Maven resolution, and module-name mismatches. - Use Case: An iOS team using Tuist wants to embed a React Native onboarding flow without installing Node; the skill guides building an XCFramework and calling ReactNativeHostManager.shared.initialize() in the AppDelegate. ## Quick Start Ask the assistant to help you add React Native to your existing native app and decide between the isolated and integrated brownfield approaches.
