A monthly release cadence for React Native

Re:A monthly release cadence for React Native by oakesm9 on Monday January 09, 2017 @03:10PM (#13359381)

That's partly true, however as someone who uses React Native with multiple production apps, having "real" native experience is invaluable when using React Native. To create a good RN app you need to know how the system works and be comfortable jumping to the native side when needed. If you don't you're bound to create a sub-par app by trying to make everything fit into the web side which is all you know.

It is possible to create an app without native experience, but it is still needed to create a very good app.

[ Parent | on HN ]

Re:A monthly release cadence for React Native by sandGorgon on Monday January 09, 2017 @04:02PM (#13359762)

we have been struggling with the idea if whether to start using react native in our current production android app.

what is a good balance between RN vs pure native? what works and what doesn't?

what about other considerations like power consumption..file size, etc?

[ Parent | on HN ]

Re:A monthly release cadence for React Native by hafor on Monday January 09, 2017 @06:58PM (#13361187)

In terms of how much React/JavaScript code you should expect to write vs. how much Native code for a production app, it obviously depends a lot on the app but maybe 80/20 might be a reasonable (if totally arbitrary) expectation.

Here's a good high-level talk which touches on the balance somewhat: https://www.youtube.com/watch?v=abSNo2P9mMM.

You should only expect to write pure native code when you hit a performance barrier with some particular custom component you're creating and there isn't an existing JS api or a standard/3rd party component which does everything you need already. But when you do hit this barrier, wiring up your own natively implemented module is pretty straightforward.

[ Parent | on HN ]