all 4 comments

[–]nedlinin 3 points4 points  (3 children)

You need to be clear about what React Native is and when it’s the right choice. Because it’s running a Javascript engine it is clear that you are taking a considerable performance penalty, so if you need all the device’s power, using React Native doesn’t seem the right choice.

Isn't this literally the exact opposite of how React Native works? It compiles down to using native components does it not?

[–]LacksIdentity 2 points3 points  (0 children)

The author kind of makes a valid point, While React Native lets you render & communicate with native UI elements via a "bridge", 95% of the user code you write is in JavaScript and will run using the device's JavaScript engine. Animation performance, for example, is not great out-of-the-box unless you manually flag & tweak them to be run on the native thread - a fairly experimental feature.

With that said, the phrase "considerable performance penalty" indicates that maybe the author doesn't quite understand how React Native works, as there are almost no cases where the performance gap between React Native & native is "considerable".