In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won't work well with RN), then deploy to both at once. We have had excellent results.
IMO RN is no exception to the Simple vs Easy trade-off [1] Not to mention using RN gives FB a legal blank check from your company [2]
[1] http://chrisfrost.com/wp-content/uploads/SimpleVsEasy-478x51...
[2] https://medium.com/@raulk/if-youre-a-startup-you-should-not-...
I don't think you contradicted anything I said. I would say special camera apps, multi-threading etc. are not needed that often.
As for slower build times, that is the beauty of RN. Building is not needed most of the time just an initial build and a rebuild every time some of the base configurations change or you are creating code outside of RN.
Ah, thanks for the update, glad they did that
> are not needed that often
Right - statistically most apps are probably throwaway code for hackathons or demos. However, I'd venture to say that >50% of serious apps will end up needing performance boosts from native code.
> Building is not needed most of the time
You need to rebuild every time you make a change in native code (obj-c or swift). Hot reloading is cool for JS changes, but bloat from RN becomes a nightmare when debugging obj-c or swift issues.
Tbh, I'm not sure how many use cases don't fit either React Native or Unity, I'd practically never choose to do an app another way these days.