React Native App Examples: What the Famous Ones Tell You About Your App
If you’re weighing React Native for an app you’re about to commission, you’ve probably already found the lists. Search for React Native app examples and you get page after page of logos, from Facebook and Instagram to Shopify, Walmart and Microsoft Teams, sorted by industry and sometimes running past a hundred entries. They exist to prove the framework is legitimate, and on that point they made their case years ago, since some of the most heavily used consumer apps in the world run at least partly on React Native.
What those lists rarely say is how each company used React Native, and that’s the part that tells you something about your own project. Some of the apps on them were built in React Native from end to end. Others are large native apps where React Native runs a handful of screens that were added one at a time. Both are real uses of the framework, but they prove different things, and only one of them looks like the decision in front of you when you’re paying for a new app.
Why the usual list of React Native apps doesn’t answer your question
A typical list puts Facebook next to Shopify’s Shop app as though they were the same kind of example. They aren’t, and the lists themselves can’t always agree on which kind an app belongs to. Netguru’s roundup describes Walmart introducing React Native into its existing native app incrementally, replacing screens module by module without a full rewrite. Pagepro’s catalog describes Walmart rewriting its mobile application and sharing 95% of the codebase between platforms. Both may have been true at different moments, but a buyer looking at a Walmart logo has no way of knowing which story it stands for.
So it’s worth sorting the examples yourself, and the sorting takes one question. For each app, ask did React Native build the whole app, or one part of it? The answer splits the famous names into two groups, and each group tells you something different.
Full builds: apps written or rebuilt entirely in React Native
The first group is the one that resembles a new commissioned app, because in each case React Native carries the whole product.
Shopify is the clearest current example. According to Netguru, Shopify rebuilt its Shop app entirely in React Native, reached 86% code unification across iOS and Android, and removed 1.8 million lines of redundant code along the way. Pagepro reports that by 2025 Shopify had finished moving its flagship app to React Native as well, after early trials in which developers rewriting its Arrive app said they felt twice as productive.
Discord built its iOS app with React Native as soon as the framework was released, and Pagepro notes that it’s maintained by three core iOS engineers. A messaging app where new content arrives all the time is a useful counterweight to the common worry that React Native only suits simple, static apps.
Coinbase Wallet runs on React Native too, and Netguru’s description of it is the most instructive of the group. The app uses custom native modules for cryptographic key handling and secure enclave access, which means that even a full React Native build drops down into native code where the phone’s hardware security demands it. That’s a normal part of building with the framework, and it’s worth knowing about before you look at your own feature list.
What this group tells you is that React Native can carry an entire consumer app, including one that handles live messaging or security-sensitive work, as long as the native pieces are planned from the start. If you’re commissioning a new app from nothing, these are the examples that look most like your situation.
Brownfield: React Native inside an existing native app
The second group is what engineers call brownfield adoption, which means adding React Native to an app that already exists in native code. Most of the biggest names on the lists belong here.
React Native came out of a hackathon at Facebook, and Pagepro describes the team migrating the Events Dashboard in Facebook’s iOS app to it. Instagram integrated React Native into its existing app starting with simple features, and the code-sharing figures Pagepro reports are for individual features, such as 92% for Push Notification Settings and 99% for Post Promote. Microsoft took a similar route with Teams, using React Native inside the app without rewriting the whole thing.
This group proves something real but narrower. A large, mature native app can take on React Native a screen at a time without a rewrite and without destabilizing what’s already there. That’s valuable if you already own a native app and want to ship new features to both platforms with less duplicated work. It says much less about a brand new build, because in each of these apps React Native arrived after the core of the product had already been written in native code.
Where we’ve shipped it: the Wine Spies iOS app
Our own example belongs in the first group. For Wine Spies, we designed and built a standalone iOS app with React Native that brings the full Wine Spies experience to mobile customers. It’s a much smaller app than Shopify’s, but we built it from scratch ourselves, so we can talk about it from the inside instead of through someone else’s case study.
It also shows something the logo lists leave out, which is that the app is one piece of a larger engagement. The Wine Spies project page lists mobile applications alongside feature development, custom design, API integrations, Rails upgrades, test coverage and CI/CD setup, and it covers the results of that work and how long the relationship has run. When any agency shows you a React Native app in its portfolio, including us, it’s fair to ask which group the app belongs to and what else they built and maintained around it.
What the examples can’t tell you about your own app
None of these examples tells you whether your app’s feature list suits React Native. Shopify’s success says little about an app whose main job happens through the camera, and Instagram’s notification settings screen says nothing about one that has to keep tracking location in the background. Our post on React Native for mobile app development walks through how to sort your own features and spot the ones that point toward native code.
Once you’ve decided React Native fits, the next question is who builds it. When a vendor shows you examples, ask whether each one was a full build or a brownfield addition, which native modules it needed, and who maintains it today. Our post on React Native consulting covers the rest of the questions worth putting to a vendor before you hire them, and our post on mobile app maintenance explains what keeping a React Native app healthy involves after launch.
Where to start
Write down the five or six things your users will do most often in the app, and note any that lean on the camera, background work or a platform-specific feature. Then set that list against the full-build examples above and see which ones it resembles. If you’d like a second opinion on what you find, you can book an intro call and bring the list with you, which is enough for a first conversation about whether React Native fits your app.