Let’s start with answering the question: what is a brownfield application?  

The term “brownfield” implies something built with already existing elements. Originally used in urban planning to describe areas that can be repurposed, it was later adopted in mobile app development. A brownfield app is basically an app which is not built from scratch.

What does it mean in practice? It means that we want to run a React Native application as a part of a native app that is already developed with technologies like Java or Kotlin. In other words, we want to integrate React Native in an existing app.

How does it work?

Let’s assume that we have a native Android application where we want to create a new screen using a React Native app that is already implemented. That screen will navigate to another screen inside the React Native application.

Navigation screen inside the React Native
react-native brownfield app

In order to make it work, we need to do a few things.

Add React Native to the project:

  • First of all, we need to add an entry for the local React Native maven directory to the project’s build.gradle. Let’s add it to the allprojects block, above other maven repositories
  • Add react-native from node_modules (thanks to change from the previous point) as a dependency to app’s build.gradle
  • Add autolinking command to at the end of app’s build.gradle

Run a React Native app:

In order to run our React Native app we are going to:

  • Create an Activity that implements DefaultHardwareBackBtnHandler interface and uses Theme.AppCompat.Light.NoActionBar theme because some React Native UI components rely on it.
  • Create ReactRootView instance inside onCreate method
  • Create ReactInstanceManager instance with needed parameters
  • Start react-native application within created root view using startReactApplication method where the second parameter is the same string as in AppRegistry.registerComponent() in index.js file.
  • Set react-native root view as activity content view

Now we are able to run our react-native app by starting ReactNativeActivity but we need still add some code to get all things to work 🙂

  • Pass activity lifecycle callbacks to the ReactInstanceManager and ReactRootView
  • Pass the back button events to avoid closing ReactNativeActivity when hardware back button is pressed and support hardware back button on JS side

Note: Even with this change we don’t have a mechanism to back to native screen w/o using hardware back button. This issue could be solved by react-native native module which will expose the method to JS that will finish ReactNativeActivity.

Additional points:

  • In debug mode, we need packager to serve JS bundle. To make it possible we need internet permissions. Add the following line to the AndroidManifest.xml file.

Note: Starting with Android 9 (API level 28), cleartext traffic is disabled by default. This prevents your application from connecting to the React Native packager. To solve this we need to add usesCleartextTraffic option to your Debug AndroidManifest.xml.

  • To enable Dev Menu in react-native app add DevSettingsActivity to AndroidManifest.xml

All of the additional points are required only for debug builds where we reload JS code from the development server, so you can strip this in release builds.

I think that all of those steps above are repeated in almost all react-native brownfield android app. But can’t it be done a bit simpler? Do we really need care about passing onPause, onDestroyetc?

Of course, it might be easier 🙂 We can use react-native-brownfield package which will help us with navigation’s issues and provide a nice API to run a react-native application.

How does it work with React Native brownfield?

We want to achieve exactly the same effect as before but we will use react-native-brownfield library

React Native screen
react-native brownfield app

Add React Native to the project:

The theory is the same as I described in the previous part of this article but with some facilities. In order to run our react-native app in native one using react-native-brownfield we need to add that package as a dependency to package.json using:


Next, we need to add react-native app as we did in Add react-native to project point.

Additional steps:

All additional steps are needed to be added here as well and only for debug builds.

Run a React Native app:

And now the fun begins 🙂 Instead of creating a root view and instance manager by ourselves we can simply use ReactNativeBrownfield package. Since autolinking script to build.gradle and react-native-brownfield are added we can use that package without additional effort.

  • Add ReactNativeActivity to AndroidManifest.xml file
  • Initialize react-native app with context as a first parameter (this in the snippet below)
  • Start react-native app
  • Create ReactNativeActivity Intent with context and moduleName as parameters and star activity.

And voilà! We are ready to go 🙂 We don’t have to worry about passing activity lifecycles, back button events or native module that enable to back from react-native to native screen. All of those things are handled by react-native-brownfield package.


Lastly, it is a popular thing to use react-native within existing native apps especially by larger organizations that have multiple teams working on the same app for multiple platforms. Thanks to react-native-brownfield the integration is easier, enjoyable and some issues that exist in every react-native brownfield app are solved 🙂

Working examples of using React Native brownfield are inside example directory.