Glad you liked the article. I haven’t considered creating my own MainReactPackage but that’s an interesting idea I’ll have to research further. The OkHttp version issue I mentioned in my post hasn’t been an issue recently, but I included it to highlight the possibility of similar conflicts in the future.

As for bridging your network calls, this can save time if you already have a lot of well tested native code you want to reuse, but in my experience, implementing strongly typed API requests across the bridge for both Android and iOS is not fun. What’s more, you’ll need an app store release if changes have to be made to bridged networking code. For these reasons, I think calls to native code across the bridge should be kept to a minimum.

One thing that surprised me when making API requests to a GraphQL endpoint from JavaScript is that the cookie based auth token from the native side was automatically shared with React Native. Depending on your authentication method, this may not work for you, but you may not have to do any extra work from an auth perspective if you make the API requests from JavaScript.

Staff Android Engineer @ Ibotta, ProAndroidDev editor

Staff Android Engineer @ Ibotta, ProAndroidDev editor