Ask HN: Companies who adopted React Native over a year ago, do you regret it?
I have been leading two React Native projects for most of 2017 with experience using the platform since early 2016.  I would definitely recommend it today.<p>The two pain points have been 3rd party native modules and platform upgrades but both situations have improved greatly in the last year.  Both the platform and the major 3rd party native modules have stabilized a lot, and platform upgrades are pretty easy via the react-native-git-upgrade tool.<p>I&#x27;ve used React Native with a number of languages: JavaScript, JavaScript + Flow, TypeScript and ClojureScript.  All of the above, and soon, if not already, ReasonML, are viable language choices.  My personal preference is TypeScript and ClojureScript.<p>The projects I have worked on professionally tend to be highly company branded with a common UI, and I am able to share ~100% of the JavaScript code-base between them (ignoring platform entry points).<p>An anecdote: recently one of the applications (React Native + TypeScript) was audited by a respected independent security consulting firm to rave reviews by the security team.  On the spectrum of risk (Info, Low, Medium, High, Critical) the worst reported issue was a Medium that was due to the platform default ProGuard setting that disabled binary obfuscation for development; enabling required a 1 line config change.