To the extent I have used RN, I find the good parts to be: - Fast & iterative development - If you are web developer, easy to switch to this (duh!) - The "Rea

To the extent I have used RN, I find the good parts to be: - Fast & iterative development - If you are web developer, easy to switch to this (duh!) - The "React" philosophy of "diffing" and pushing changes and having a virtual DOM - Javascript - less boiler plate and easier to write (YMMV) But, with RN you hit the limits in some spots: - Handling navigation. The available navigator components are difficult to work with. The idioms are little sticky. I know they've started working on a new one - With Android SDK, you have the full set of components available and hence more choices - components, Material themes etc., - Because of the above point, you are always ahead, unless you have bandwidth to write wrappers for new components/ changes - Slightly noticeable lesser frame rates compared to native. I don;t think this is a deal-breaker though. Overall, the RN team is doing a great job by bringing the well tested RN concept to the mobile world and making "reusable code" worth an attempt. The choice depends on one's requirements and technology choices available in the project etc.,