After my last post I decided to see how difficult it would be to add React Native to an existing Android application. Turns out not that hard! (Although there are still a few gotcha’s).
The purpose of this post is really just getting from 0 to “hello world” with React Native in an existing app. The idea is to create an activity where React Native renders the view. I haven’t tried any 2-way communication between the JS/Java, or any more complicated integrations. If we go forward with actually building future functionality for Emberall in React Native I’ll certainly have more to say. And you won’t find any instructions here for cross-platform (iOS) support – adding React Native as a dependency obviously won’t magically make your app compile on iOS.
Before following these steps, make sure you’re able to get a “Hello World” React Native project compiling/running from your machine on your device. Follow the instructions at Getting Started if you haven’t yet gone through the process.
react-native init TempProjectin a temporary directory.
TempProjectto the root of your Android project.
- In the root of your Android project, run
- In your app’s
compile 'com.facebook.react:react-native:0.11.+'to the
- In your
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
- Create a new activity in your app like normal. Copy in the methods from this gist, customizing them as necessary.
- (Optional) add “node_modules/” to your
You should now be able to run your app, and the view for your new activity will be rendered with React Native. All the dev tools, hot reloading etc. should work as intended.
I ran into a couple of issues just in getting this far:
- If you have any 64-bit dependencies or libraries, React Native won’t load on 64-bit devices because it only provides 32-bit binaries for the JSC interop. I opened an issue about this and have also provided a workaround.
- Oddly, the dev options menu accessed through “Rage Shake” > “Dev Settings” pulls in any existing
PreferenceScreenyour app has instead of loading the React Native preferences. This is likely a bug in how React Native is implemented and I may open a PR if I have time to investigate the exact issue.