
Mobile app development
Add React Native to the Signal open source app — part 1 (iOS)
Mariusz Stanisz•As core contributors to React Native and the engineers behind expo-brownfield, we've built the tooling that makes it easier. We'll help you use it.
We created and upstreamed expo-brownfield – the official Expo package for adding React Native to existing native apps. Expo shipped it as part of SDK 55. When we help you with brownfield integration, we work in tooling we understand under the hood.
Deep framework knowledge built through years of active contribution, not just usage.
We stay close to where teams actually ship React Native, including brownfield projects.
We help shape the future of the framework alongside Meta, Vercel, and Expo.
The library we built to automate brownfield setup is now the approach Expo officially recommends.
We meet you wherever you are in the process – from first setup to ongoing maintenance.
We configure the React Native runtime, set up your build pipeline, and embed React Native into your native navigation cleanly. Whether you want to run one screen in production or migrate an entire feature area, we make sure the integration fits your architecture and release process.
Using expo-brownfield, we can package your React Native code as a native binary artifact – XCFramework for iOS, AAR for Android – that your native team consumes like any other dependency. No React Native build dependencies, no shared toolchain; their workflow doesn't change.
If you already have native screens you want to move to React Native, we can write the code and handle the coordination. You end up with less duplication and one shared codebase across both iOS and Android.
Migration is a process. Whether you're starting fresh or already have a brownfield setup that needs work – a React Native bump, a performance issue, a tricky integration – we can pick it up wherever you are.
The library we built to automate brownfield setup for Expo projects shipped as part of SDK 55. What started as an internal tool is now the approach Expo officially recommends.
Mariusz Stanisz at App.js Conf 2024 on what happens when you push brownfield React Native beyond the basics: connecting two large standalone apps, navigating edge cases the docs don't cover, and what it actually takes to ship it.
Signal has years of native decisions baked in, custom build configurations, and no margin for error. This walkthrough covers what it actually takes to get React Native running inside an app like that.
“We have grown to trust Software Mansion to the point where we have them build significant parts of our core technology alongside our own team. Our software products wouldn't be as far along today if we didn't have Software Mansion's help along the way.”

A commit-by-commit walkthrough of the integrated brownfield approach using Expo: two-way navigation between native Activities and React Native screens, Kotlin native modules, and EAS Build.
You have a native app that works, you want to extend it. Tell us where you are and what you're trying to add, and we'll figure out together whether brownfield is the right move and what it would take during a short call.