The Truth About React Native

React Native’s popularity is real—but the public narrative around it is often sloppy. A long-form rebuttal argues that common claims about which companies “use React Native” (and how much) get distorted by documentation shortcuts, app-store linkages, and a failure to distinguish between an entire app being built in React Native versus React Native being used for specific screens, modules, or embedded UI inside a larger native codebase. That nuance matters because React Native is designed to integrate with existing native apps, letting teams “vertically slice” ownership (ads, feed, messages, etc.) without forcing every part of a massive app into one technology stack.

The critique targets a React Native showcase list hosted on Meta’s Open Source documentation, where apps are presented as React Native even when the main app experience may not be. The rebuttal’s central counterpoint is that “React Native used somewhere” is not the same as “React Native is the whole app,” and that many companies build multiple apps and internal tools—so a single missing file or a non-React Native main shell doesn’t disprove React Native usage. Walmart becomes the flashpoint: the showcase links to the Walmart app, but the rebuttal claims the main Walmart app isn’t React Native while other Walmart mobile products and internal fulfillment tools likely are, supported by ongoing hiring for React Native roles. The argument is that the docs’ linking choices are misleading, but the conclusion “Walmart doesn’t use React Native” is equally unwarranted.

The rebuttal then drills into Meta-owned examples. It says the Facebook iOS app isn’t “root-built” entirely in React Native, yet major sections—especially Marketplace—are built with React Native on both iOS and Android. It also emphasizes Meta’s internal component architecture (Component Kit) and points to how React Native is used to reduce complexity in specific areas that need faster iteration. A further claim is that React Native for web is not a major part of Meta’s approach; instead, React Native is used as a native rendering layer on mobile, translating React’s component model into platform-native primitives.

The most concrete popularity evidence comes later: a reverse-engineering approach that checks the top 100 apps in multiple App Store categories. In the cited results from March 21, roughly a quarter of top apps in categories like Sports, Shopping, Entertainment, Food, Business, and Medical use React Native—suggesting it’s far from niche in mainstream consumer apps. The rebuttal also argues that job-market demand supports this: Indeed listings reportedly show hundreds of React Native roles versus far fewer for SwiftUI and Jetpack Compose.

Finally, the rebuttal challenges the “marketing bias” angle. It concedes that consultancies and framework influencers can produce promotional content, but argues that accusing React Native consulting groups of fabricating usage ignores how often large companies independently adopt React Native for real engineering needs. Amazon is presented as a key example: an Amazon engineer describes React Native usage across shopping, music, photos, and even Kindle device UI, plus a large internal interest group of engineers sharing modules.

Overall, the message is not that every claim in the original showcase is perfect, but that the counter-narrative—React Native is broadly used and increasingly adopted—survives contact with deeper technical nuance and category-level app analysis. The bigger warning is about decision-making: clickbait framework articles, especially AI-generated ones, can mislead beginners, and better reporting requires going beyond surface-level links into how teams actually ship UI across platforms.