As a full-time native app developer on both platforms for 10 years, I find this argument odd.
It’s trivial to interface existing native code with react-native. I’ve “merged” two existing apps written on both platforms into react-native apps by adding only a small amount of JS (and some native RN interfacing) with removing zero native code on either platform. Likewise, I’ve started with full Javascript apps and slowly replaced the JS with native code where perf mattered or RN was lacking.
You can choose how much “react-ness” is in your app quite easily, and to me this is the real game changer for react-native.
the official docs worked for me.[0]
Biggest “gotcha” in my experience is version mis-match hell. Each major RN version supports a very precise version of Xcode and Android build tools/targets etc. Read the RN version release notes and you’ll be okay.
It’s trivial to interface existing native code with react-native. I’ve “merged” two existing apps written on both platforms into react-native apps by adding only a small amount of JS (and some native RN interfacing) with removing zero native code on either platform. Likewise, I’ve started with full Javascript apps and slowly replaced the JS with native code where perf mattered or RN was lacking.
You can choose how much “react-ness” is in your app quite easily, and to me this is the real game changer for react-native.