Skip to main content
Version: Next

Integration with Existing Apps

React Native is great when you are starting a new mobile app from scratch. However, it also works well for adding a single view or user flow to existing native applications. With a few steps, you can add new React Native based features, screens, views, etc.

The specific steps are different depending on what platform you're targeting.

Key Concepts#

The keys to integrating React Native components into your Android application are to:

  1. Set up React Native dependencies and directory structure.
  2. Develop your React Native components in JavaScript.
  3. Add a ReactRootView to your Android app. This view will serve as the container for your React Native component.
  4. Start the React Native server and run your native application.
  5. Verify that the React Native aspect of your application works as expected.

Prerequisites#

Follow the React Native CLI Quickstart in the environment setup guide to configure your development environment for building React Native apps for Android.

1. Set up directory structure#

To ensure a smooth experience, create a new folder for your integrated React Native project, then copy your existing Android project to an /android subfolder.

2. Install JavaScript dependencies#

Go to the root directory for your project and create a new package.json file with the following contents:

{  "name": "MyReactNativeApp",  "version": "0.0.1",  "private": true,  "scripts": {    "start": "yarn react-native start"  }}

Next, make sure you have installed the yarn package manager.

Install the react and react-native packages. Open a terminal or command prompt, then navigate to the directory with your package.json file and run:

$ yarn add react-native

This will print a message similar to the following (scroll up in the yarn output to see it):

warning "react-native@0.52.2" has unmet peer dependency "react@16.2.0".

This is OK, it means we also need to install React:

$ yarn add react@version_printed_above

Yarn has created a new /node_modules folder. This folder stores all the JavaScript dependencies required to build your project.

Add node_modules/ to your .gitignore file.

Adding React Native to your app#

Configuring maven#

Add the React Native and JSC dependency to your app's build.gradle file:

dependencies {    implementation "com.android.support:appcompat-v7:27.1.1"    ...    implementation "com.facebook.react:react-native:+" // From node_modules    implementation "org.webkit:android-jsc:+"}

If you want to ensure that you are always using a specific React Native version in your native build, replace + with an actual React Native version you've downloaded from npm.

Add an entry for the local React Native and JSC maven directories to the top-level build.gradle. Be sure to add it to the “allprojects” block, above other maven repositories:

allprojects {    repositories {        maven {            // All of React Native (JS, Android binaries) is installed from npm            url "$rootDir/../node_modules/react-native/android"        }        maven {            // Android JSC is installed from npm            url("$rootDir/../node_modules/jsc-android/dist")        }        ...    }    ...}

Make sure that the path is correct! You shouldn’t run into any “Failed to resolve: com.facebook.react:react-native:0.x.x" errors after running Gradle sync in Android Studio.

Enable native modules autolinking#

To use the power of autolinking, we have to apply it a few places. First add the following entry to settings.gradle:

apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)

Next add the following entry at the very bottom of the app/build.gradle:

apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)

Configuring permissions#

Next, make sure you have the Internet permission in your AndroidManifest.xml:

<uses-permission android:name="android.permission.INTERNET" />

If you need to access to the DevSettingsActivity add to your AndroidManifest.xml:

<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />

This is only used in dev mode when reloading JavaScript from the development server, so you can strip this in release builds if you need to.

Cleartext Traffic (API level 28+)#

Starting with Android 9 (API level 28), cleartext traffic is disabled by default; this prevents your application from connecting to the Metro bundler. The changes below allow cleartext traffic in debug builds.

1. Apply the usesCleartextTraffic option to your Debug AndroidManifest.xml#

<!-- ... --><application  android:usesCleartextTraffic="true" tools:targetApi="28" >  <!-- ... --></application><!-- ... -->

This is not required for Release builds.

To learn more about Network Security Config and the cleartext traffic policy see this link.

Code integration#

Now we will actually modify the native Android application to integrate React Native.

The React Native component#

The first bit of code we will write is the actual React Native code for the new "High Score" screen that will be integrated into our application.

1. Create a index.js file#

First, create an empty index.js file in the root of your React Native project.

index.js is the starting point for React Native applications, and it is always required. It can be a small file that requires other file that are part of your React Native component or application, or it can contain all the code that is needed for it. In our case, we will put everything in index.js.

2. Add your React Native code#

In your index.js, create your component. In our sample here, we will add a <Text> component within a styled <View>:

import React from 'react';import {  AppRegistry,  StyleSheet,  Text,  View} from 'react-native';
const HelloWorld = () => {  return (    <View style={styles.container}>      <Text style={styles.hello}>Hello, World</Text>    </View>  );};var styles = StyleSheet.create({  container: {    flex: 1,    justifyContent: 'center'  },  hello: {    fontSize: 20,    textAlign: 'center',    margin: 10  }});
AppRegistry.registerComponent(  'MyReactNativeApp',  () => HelloWorld);
3. Configure permissions for development error overlay#

If your app is targeting the Android API level 23 or greater, make sure you have the permission android.permission.SYSTEM_ALERT_WINDOW enabled for the development build. You can check this with Settings.canDrawOverlays(this);. This is required in dev builds because React Native development errors must be displayed above all the other windows. Due to the new permissions system introduced in the API level 23 (Android M), the user needs to approve it. This can be achieved by adding the following code to your Activity's in onCreate() method.

private final int OVERLAY_PERMISSION_REQ_CODE = 1;  // Choose any value
...
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {    if (!Settings.canDrawOverlays(this)) {        Intent intent = new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION,                                   Uri.parse("package:" + getPackageName()));        startActivityForResult(intent, OVERLAY_PERMISSION_REQ_CODE);    }}

Finally, the onActivityResult() method (as shown in the code below) has to be overridden to handle the permission Accepted or Denied cases for consistent UX. Also, for integrating Native Modules which use startActivityForResult, we need to pass the result to the onActivityResult method of our ReactInstanceManager instance.

@Overrideprotected void onActivityResult(int requestCode, int resultCode, Intent data) {    if (requestCode == OVERLAY_PERMISSION_REQ_CODE) {        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {            if (!Settings.canDrawOverlays(this)) {                // SYSTEM_ALERT_WINDOW permission not granted            }        }    }    mReactInstanceManager.onActivityResult( this, requestCode, resultCode, data );}

The Magic: ReactRootView#

Let's add some native code in order to start the React Native runtime and tell it to render our JS component. To do this, we're going to create an Activity that creates a ReactRootView, starts a React application inside it and sets it as the main content view.

If you are targeting Android version <5, use the AppCompatActivity class from the com.android.support:appcompat package instead of Activity.

public class MyReactActivity extends Activity implements DefaultHardwareBackBtnHandler {    private ReactRootView mReactRootView;    private ReactInstanceManager mReactInstanceManager;
    @Override    protected void onCreate(Bundle savedInstanceState) {        super.onCreate(savedInstanceState);        SoLoader.init(this, false);
        mReactRootView = new ReactRootView(this);        List<ReactPackage> packages = new PackageList(getApplication()).getPackages();        // Packages that cannot be autolinked yet can be added manually here, for example:        // packages.add(new MyReactNativePackage());        // Remember to include them in `settings.gradle` and `app/build.gradle` too.
        mReactInstanceManager = ReactInstanceManager.builder()                .setApplication(getApplication())                .setCurrentActivity(this)                .setBundleAssetName("index.android.bundle")                .setJSMainModulePath("index")                .addPackages(packages)                .setUseDeveloperSupport(BuildConfig.DEBUG)                .setInitialLifecycleState(LifecycleState.RESUMED)                .build();        // The string here (e.g. "MyReactNativeApp") has to match        // the string in AppRegistry.registerComponent() in index.js        mReactRootView.startReactApplication(mReactInstanceManager, "MyReactNativeApp", null);
        setContentView(mReactRootView);    }
    @Override    public void invokeDefaultOnBackPressed() {        super.onBackPressed();    }}

If you are using a starter kit for React Native, replace the "HelloWorld" string with the one in your index.js file (it’s the first argument to the AppRegistry.registerComponent() method).

Perform a “Sync Project files with Gradle” operation.

If you are using Android Studio, use Alt + Enter to add all missing imports in your MyReactActivity class. Be careful to use your package’s BuildConfig and not the one from the facebook package.

We need set the theme of MyReactActivity to Theme.AppCompat.Light.NoActionBar because some React Native UI components rely on this theme.

<activity  android:name=".MyReactActivity"  android:label="@string/app_name"  android:theme="@style/Theme.AppCompat.Light.NoActionBar"></activity>

A ReactInstanceManager can be shared by multiple activities and/or fragments. You will want to make your own ReactFragment or ReactActivity and have a singleton holder that holds a ReactInstanceManager. When you need the ReactInstanceManager (e.g., to hook up the ReactInstanceManager to the lifecycle of those Activities or Fragments) use the one provided by the singleton.

Next, we need to pass some activity lifecycle callbacks to the ReactInstanceManager and ReactRootView:

@Overrideprotected void onPause() {    super.onPause();
    if (mReactInstanceManager != null) {        mReactInstanceManager.onHostPause(this);    }}
@Overrideprotected void onResume() {    super.onResume();
    if (mReactInstanceManager != null) {        mReactInstanceManager.onHostResume(this, this);    }}
@Overrideprotected void onDestroy() {    super.onDestroy();
    if (mReactInstanceManager != null) {        mReactInstanceManager.onHostDestroy(this);    }    if (mReactRootView != null) {        mReactRootView.unmountReactApplication();    }}

We also need to pass back button events to React Native:

@Override public void onBackPressed() {    if (mReactInstanceManager != null) {        mReactInstanceManager.onBackPressed();    } else {        super.onBackPressed();    }}

This allows JavaScript to control what happens when the user presses the hardware back button (e.g. to implement navigation). When JavaScript doesn't handle the back button press, your invokeDefaultOnBackPressed method will be called. By default this finishes your Activity.

Finally, we need to hook up the dev menu. By default, this is activated by (rage) shaking the device, but this is not very useful in emulators. So we make it show when you press the hardware menu button (use Ctrl + M if you're using Android Studio emulator):

@Overridepublic boolean onKeyUp(int keyCode, KeyEvent event) {    if (keyCode == KeyEvent.KEYCODE_MENU && mReactInstanceManager != null) {        mReactInstanceManager.showDevOptionsDialog();        return true;    }    return super.onKeyUp(keyCode, event);}

Now your activity is ready to run some JavaScript code.

Test your integration#

You have now done all the basic steps to integrate React Native with your current application. Now we will start the Metro bundler to build the index.bundle package and the server running on localhost to serve it.

1. Run the packager#

To run your app, you need to first start the development server. To do this, run the following command in the root directory of your React Native project:

$ yarn start
2. Run the app#

Now build and run your Android app as normal.

Once you reach your React-powered activity inside the app, it should load the JavaScript code from the development server and display:

Screenshot

Creating a release build in Android Studio#

You can use Android Studio to create your release builds too! It’s as quick as creating release builds of your previously-existing native Android app. There’s one additional step, which you’ll have to do before every release build. You need to execute the following to create a React Native bundle, which will be included with your native Android app:

$ npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/com/your-company-name/app-package-name/src/main/assets/index.android.bundle --assets-dest android/com/your-company-name/app-package-name/src/main/res/

Don’t forget to replace the paths with correct ones and create the assets folder if it doesn’t exist.

Now, create a release build of your native app from within Android Studio as usual and you should be good to go!

Now what?#

At this point you can continue developing your app as usual. Refer to our debugging and deployment docs to learn more about working with React Native.