4 ms·
Is there some subset of native capabilities that one can still attack with an RN codebase and not have to deal with the native <> JS issues you ran into? Say, m
by sameers 8y ago
Is there some subset of native capabilities that one can still attack with an RN codebase and not have to deal with the native <> JS issues you ran into? Say, my app "only" needed to access contacts and images (no GPS; no bluetooth; not take pictures; not worry about accelerometer; etc.) - in your experience, does that put RN back in the picture (somewhat)?
- tspike 8y agoYou can do just about everything a native app can do with RN. If you have a very small, capable team that's all on the same page, it's a good choice. For large existing codebases in large organizations, it's a very poor choice.
- kanalas 8y agoHaving worked alone with react-native for about 3 months now and building our production application, I'll go further and state that for certain kinds of tasks React Native is definitely the way to go, but if the requirements seek heavy background work or involving multiple threads native code seems to be way to go. I'd love to hear your thoughts on Flutter. Cross compiling to native seems to give us the gains with respect to almost close to native performance too.