The cross-platform vs native debate has a quality problem: the people most qualified to give objective assessments have financial or professional stakes in one answer. Agency developers who charge by the hour prefer native because it doubles the billable work. Cross-platform framework vendors publish benchmark comparisons designed to minimize the gaps between their output and native. Native platform advocates at Apple and Google have obvious incentives to characterize cross-platform output as inferior.

Google’s decision to build Flutter on top of Dart — a language that had minimal developer mindshare and an uncertain future when Flutter launched — was a risk that the broader developer community viewed with skepticism. Dart was not JavaScript. It was not Kotlin. It was not a language that developers had strong feelings about because most developers had never used it. Building a cross-platform UI framework on an obscure language was, on its face, an unusual strategic choice.

React Native was announced by Facebook in 2015 with a promise that rewrote the calculus of mobile development: learn once, write anywhere. The promise was qualified from the start — React Native was never write once, run anywhere in the way that early web-based mobile frameworks had claimed to be — but it was credible enough to reshape how a generation of mobile teams made technology decisions.

Eleven years later, React Native is used in production by Microsoft, Shopify, Coinbase, and thousands of smaller organizations. It has survived the emergence of Flutter, the maturation of Kotlin Multiplatform, and a period of internal uncertainty at Meta when the framework’s future was genuinely in question. Its survival reflects something real about the problem it solves and the ecosystem it has built.