<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi" -->

---
title: You Don’t Need a Rewrite: Expo’s New Brownfield React...
description: Expo's new expo-brownfield package removes many of the challenges of adding React Native to existing native iOS and Android apps. Starting with SDK 54,...
canonical: https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: You Don’t Need a Rewrite: Expo’s New Brownfield React Native Story | daily.dev
og:description: Expo's new expo-brownfield package removes many of the challenges of adding React Native to existing native iOS and Android apps. Starting with SDK 54,...
og:url: https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi
og:image: https://api.daily.dev/og/posts/58dLgMHDI.png
og:image:alt: You Don’t Need a Rewrite: Expo’s New Brownfield React Native Story
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# You Don’t Need a Rewrite: Expo’s New Brownfield React Native Story

**[Infinite Red \(Red Shift\)](https://daily.dev/sources/infinite-red)** · 7 min read · 4 upvotes · 3 comments

## Summary

Expo's new expo-brownfield package removes many of the challenges of adding React Native to existing native iOS and Android apps. Starting with SDK 54, directory restructuring is no longer required and all Expo packages were bug-hunted for brownfield compatibility. SDK 55 adds an 'isolated' integration option, letting React Native code live in its own codebase and ship as a native library, so native engineers don't need to worry about Node, yarn, or Metro. An agent skill automates many of the routine setup steps, and the team is prompted with 'add Expo to this app'. The Expo team set a goal to integrate React Native into 100 open-source native apps.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://shift.infinite.red/you-dont-need-a-rewrite-expo-s-new-brownfield-react-native-story-c072b4e971dd>

## Questions this post answers

### How do I add React Native to an existing native iOS or Android app without rewriting it?

Use the official expo-brownfield package, introduced with Expo SDK 54 and 55, which lets React Native screens sit alongside existing native screens without restructuring directories. SDK 55 adds an 'isolated' option where React Native code lives in a separate repo and compiles into a native library that native engineers add like any third-party dependency, with no Node or Metro setup required.

_Teams weighing a React Native rewrite versus incremental adoption can track tooling updates like this on daily.dev._

### Do all Expo packages work in brownfield (native + React Native) apps?

Yes, as of Expo SDK 54, the Expo team ran a dedicated bug hunt to ensure all Expo packages are brownfield-compatible, removing prior trade-offs where some packages only worked in fully React Native projects. This means developers no longer need to choose between using Expo's package ecosystem and integrating React Native into an existing native codebase.

_Developers evaluating Expo's package coverage before integrating can keep tabs on SDK changes via daily.dev._

### What is the difference between the integrated and isolated approaches to adding React Native with Expo SDK 55?

The integrated approach puts React Native code directly inside the native app repo, suiting a single team sharing native and React Native code. The isolated approach, new in SDK 55, builds React Native functionality as a separate app and compiles it into a native library via expo-brownfield's build command, letting separate teams keep their own release cadence without native engineers needing a React Native dev environment.

_Teams choosing a brownfield integration strategy can follow these architecture options on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@andruhudz** · 0 upvotes

> It looks like in AI Epoch we can write on something native like  Swift or Kotlin with better performance

**@andruhudz** · 0 upvotes

> For instance like Shopify did. Now to rewrite it's more easily than ever

**@pdfopsdev** · 0 upvotes

> isolated mode is the interesting part imo, every brownfield RN integration I've seen die was native engineers fighting yarn/metro version mismatches with the host app's own build. does isolated still let the RN layer share native modules with the rest of the app, or is it fully sandboxed off?

## Similar posts on daily.dev

- [From Brownfield Complexity to AI-Supported React Native Migration](https://daily.dev/posts/from-brownfield-complexity-to-ai-supported-react-native-migration-yw76oi3hy) · Callstack Blog · 0 upvotes · 0 comments
- [Debunking React Native Myths: Why Expo is Now Our Go-To \(Even for Complex Projects\)](https://daily.dev/posts/debunking-react-native-myths-why-expo-is-now-our-go-to-even-for-complex-projects--d8y2ld4kd) · Whitespectre · 35 upvotes · 1 comments
- [Making React Native actually native](https://daily.dev/posts/making-react-native-actually-native-bdan1xdzt) · Bytes by ui.dev · 2 upvotes · 0 comments
- [How we made Hybrid iOS apps compile 39% faster with React Native Brownfield](https://daily.dev/posts/how-we-made-hybrid-ios-apps-compile-39-faster-with-react-native-brownfield-pjknbygoq) · Callstack Blog · 0 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#mobile](https://daily.dev/tags/mobile), [#react-native](https://daily.dev/tags/react-native)

[View this post on daily.dev](https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"You Don’t Need a Rewrite: Expo’s New Brownfield React Native Story","url":"https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi"},"datePublished":"2026-11-22T08:49:32.146Z","dateModified":"2026-11-22T08:50:19.061Z","description":"Expo's new expo-brownfield package removes many of the challenges of adding React Native to existing native iOS and Android apps. Starting with SDK 54,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8b41ea19b4ee824acbdc913503f38af8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8b41ea19b4ee824acbdc913503f38af8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Infinite Red (Red Shift)","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Infinite Red (Red Shift)","logo":"https://media.daily.dev/image/upload/s--OO9DdSoz--/f_auto,q_auto/v1785654911/logos/infinite-red?_a=BAMAMicg0","url":"https://daily.dev/sources/infinite-red"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"ai-agents,mobile,react-native","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Infinite Red (Red Shift)","item":"https://daily.dev/sources/infinite-red"},{"@type":"ListItem","position":3,"name":"You Don’t Need a Rewrite: Expo’s New Brownfield React Native Story"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi","comment":[{"@type":"Comment","text":"It looks like in AI Epoch we can write on something native like  Swift or Kotlin with better performance","datePublished":"2026-11-22T17:59:29.733Z","url":"https://daily.dev/posts/58dLgMHDI#c-ntOI5RIiw","author":{"@type":"Person","name":"andru hudz","url":"https://daily.dev/andruhudz","image":"https://lh3.googleusercontent.com/a/ACg8ocL---snYLZfyby0hGSZRNE0HBZxFUaV8F3aRsSy8J8sc6V6Ew=s96-c"}},{"@type":"Comment","text":"For instance like Shopify did. Now to rewrite it’s more easily than ever","datePublished":"2026-11-22T18:07:03.467Z","url":"https://daily.dev/posts/58dLgMHDI#c-EkckdiH4V","author":{"@type":"Person","name":"andru hudz","url":"https://daily.dev/andruhudz","image":"https://lh3.googleusercontent.com/a/ACg8ocL---snYLZfyby0hGSZRNE0HBZxFUaV8F3aRsSy8J8sc6V6Ew=s96-c"}},{"@type":"Comment","text":"isolated mode is the interesting part imo, every brownfield RN integration I’ve seen die was native engineers fighting yarn/metro version mismatches with the host app’s own build. does isolated still let the RN layer share native modules with the rest of the app, or is it fully sandboxed off?","datePublished":"2026-11-22T18:08:56.559Z","url":"https://daily.dev/posts/58dLgMHDI#c-prdNMqiZi","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/you-don-t-need-a-rewrite-expo-s-new-brownfield-react-native-story-58dlgmhdi#faq","mainEntity":[{"@type":"Question","name":"How do I add React Native to an existing native iOS or Android app without rewriting it?","acceptedAnswer":{"@type":"Answer","text":"Use the official expo-brownfield package, introduced with Expo SDK 54 and 55, which lets React Native screens sit alongside existing native screens without restructuring directories. SDK 55 adds an 'isolated' option where React Native code lives in a separate repo and compiles into a native library that native engineers add like any third-party dependency, with no Node or Metro setup required. Teams weighing a React Native rewrite versus incremental adoption can track tooling updates like this on daily.dev."}},{"@type":"Question","name":"Do all Expo packages work in brownfield (native + React Native) apps?","acceptedAnswer":{"@type":"Answer","text":"Yes, as of Expo SDK 54, the Expo team ran a dedicated bug hunt to ensure all Expo packages are brownfield-compatible, removing prior trade-offs where some packages only worked in fully React Native projects. This means developers no longer need to choose between using Expo's package ecosystem and integrating React Native into an existing native codebase. Developers evaluating Expo's package coverage before integrating can keep tabs on SDK changes via daily.dev."}},{"@type":"Question","name":"What is the difference between the integrated and isolated approaches to adding React Native with Expo SDK 55?","acceptedAnswer":{"@type":"Answer","text":"The integrated approach puts React Native code directly inside the native app repo, suiting a single team sharing native and React Native code. The isolated approach, new in SDK 55, builds React Native functionality as a separate app and compiles it into a native library via expo-brownfield's build command, letting separate teams keep their own release cadence without native engineers needing a React Native dev environment. Teams choosing a brownfield integration strategy can follow these architecture options on daily.dev."}}]}
```

