Expo SDK 55 introduces an isolated brownfield workflow that lets teams embed Expo into existing native iOS/Android apps without a full rewrite. The new `expo-brownfield` package compiles your Expo project into a native binary artifact — an XCFramework for iOS or an AAR for Android — that native developers can consume like any other dependency, without needing a Node.js environment. A built-in bi-directional messaging API handles communication between the native host and the embedded Expo app. The post also covers limitations: only one embedded app per native app is currently supported, build times can be slow, and some libraries that assume React Native is the app entry point may not work correctly in brownfield setups.

10m read timeFrom expo.dev
Post cover image
Table of contents
Where Expo fits in existing native appsBrownfield approaches in ExpoLimitations and trade-offsWrap up

Sort: