react-native-brownfield-migration

To incrementally migrate native iOS apps to React Native, you package JavaScript code into an XCFramework and integrate it into the host app. This process involves assessing project state, generating the artifact, and ensuring proper runtime initialization and framework linking.

Choosing between Expo and bare React Native for brownfield migration requires evaluating your project files and intent. This Skill enforces a single path selection gate, asking disambiguation questions to determine whether the Expo or bare workflow best fits your host app integration needs.

Packaging a React Native brownfield AAR for Android involves using the brownfield CLI to generate the artifact and publishing it for consumption. This workflow ensures module naming and Maven or local framework linking follow recommended host integration guardrails before starting the integration.

React Native brownfield integration is the strategy of incrementally adopting React Native or Expo within existing native iOS or Android apps. You need it when introducing React Native screens or modules without rewriting the entire host application from scratch.

Limitations of @callstack/react-native-brownfield migrations include the strict requirement to choose only one Expo or bare path per task and the necessity to validate placeholder usage. You must also confirm that artifact packaging succeeds before starting any host integration steps.