expo-brownfield

Integrate Expo and React Native into existing native iOS or Android apps.

Updated May 7, 2026
One-click install
npx skills add https://github.com/softwarebyze/Backgammon-Mastermind --skill expo-brownfield
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-brownfield
Source: https://github.com/softwarebyze/Backgammon-Mastermind/tree/main/.agents/skills/expo-brownfield
Command: npx skills add https://github.com/softwarebyze/Backgammon-Mastermind --skill expo-brownfield

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams incrementally add React Native capabilities to an already-existing native iOS or Android app, using Expo’s supported brownfield integration paths instead of rewriting everything from scratch.

Core Features & Use Cases

  • Isolated brownfield integration: build a precompiled artifact (AAR/ XCFramework) that the native app consumes as a normal dependency, keeping native build tooling simple.
  • Integrated brownfield integration: wire React Native + Expo directly into the existing Gradle / CocoaPods build so the host app has a single unified build pipeline with better development iteration.
  • Decision guidance for real scenarios: choose between isolated vs integrated based on repository structure, team ownership, tooling constraints, and the need for hot reload and debugging ergonomics.

Quick Start

Tell the AI: “Our native team wants to embed React Native into an existing Swift/Kotlin app without disrupting their build tooling—should we use Expo brownfield isolated or integrated, and what files need to change?”

Frequently Asked Questions about expo-brownfield

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add React Native to an existing native iOS or Android app?

You can add React Native to an existing app via Expo brownfield integration by embedding it into your Swift/Obj-C or Kotlin/Java codebase using either a prebuilt AAR/XCFramework artifact or direct Gradle/CocoaPods build wiring.

What is the difference between isolated and integrated brownfield integration?

Isolated brownfield integration provides a precompiled AAR or XCFramework that the native app consumes as a standard dependency, while integrated brownfield wires React Native directly into your existing Gradle or CocoaPods build pipeline for unified builds and hot reload.

Should I use a prebuilt AAR/XCFramework or direct Gradle/CocoaPods integration for React Native?

Choose prebuilt AAR/XCFramework artifacts to keep native build tooling simple, or choose direct Gradle/CocoaPods integration when you need a single unified build pipeline with better development iteration and hot reload debugging ergonomics.

Does Expo brownfield integration work with my existing Swift and Kotlin codebase?

Yes, Expo brownfield integration supports embedding React Native into existing Swift/Obj-C or Kotlin/Java codebases, allowing teams to incrementally adopt React Native capabilities without rewriting their native application from scratch.

What files need to change to embed React Native into an existing native app?

Embedding React Native requires modifying native entry points, updating build configuration files, and aligning moduleName and app registration contracts to ensure the host application properly loads the React Native bundle.

What are the limitations of using prebuilt AAR and XCFramework for React Native integration?

Using prebuilt AAR and XCFramework artifacts isolates React Native from your native build tooling, which simplifies the build but limits development iteration speed and reduces hot reload and debugging ergonomics compared to direct Gradle or CocoaPods integration.