Mobile Framework for Next.js: what 54 makers' products chose
Among 54 makers' products built with Next.js that we know the mobile framework of, Expo leads: 28 of them (52%), 1.4× its share among all makers' products (36%). Next come React Native (17) and Flutter (9).
Cross-platform, native or wrapped web. Cross-platform frameworks give you both stores from one codebase with near-native UI; native gives you the closest platform fit on one platform only; wrapping your web app reuses what you have, with a less native feel.
What makers on Next.js chose
| Option | Next.js products | All makers |
|---|---|---|
| 28 (52%) | 36% | |
| 17 (31%) | 29% | |
| 9 (17%) | 34% | |
| Jetpack ComposePlatform native | 1 (2%) | 0% |
Live makers' products with a source for both: that they're built with Next.js, and what they use for mobile framework. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Which to pick, by situation
- You know React or TypeScript and want both app stores from one codebase
Expo 28 here - You're adding React Native screens to an existing native app, or need full control of the native builds
React Native 17 here - You want the same custom design on every platform and are fine learning Dart
Flutter 9 here - Your users are only on AndroidJetpack Compose 1 here
Expo
Cross-platform native28 Next.js products here (52%), against 36% of all makers' products.
In BoltBest forReact Native apps for iOS and Android, with cloud builds, store submission and over-the-air updates.
Trade-offEAS cloud services have usage-based paid tiers beyond the free tier; some native features need custom modules.
“Helped us build and deploy cross-platform updates with lightning speed. The unified codebase meant we could focus on user experience instead of device-specific headaches.”
“Because shipping on iOS and Android separately in 2025 is just self-harm. Expo lets us move fast, break nothing important, and focus on the product — not build configs and platform rituals.”
Mobile FrameworkMaker says so · source ↗“To simplify the app development and testing.”
Mobile FrameworkMaker says so · source ↗“Supercharges react-native development. And, with custom builds, you get all of this power with almost zero downside compared to developing bare react-native. Plus, EAS makes building and submitting to the App Store super simple.”
Mobile FrameworkMaker says so · source ↗“There's no way I can maintain two native codebases alone. Expo let me ship iOS and Android from the same TypeScript project I already knew.”
Mobile FrameworkMaker says so · source ↗“The deepeye iOS app is built on Expo, and it is the reason a small team shipped a native app without a native-sized timeline. Fast iteration, painless builds, and an OTA update flow that lets us push detection improvements to users the day we make them.”
Mobile FrameworkMaker says so · source ↗“I've used Expo in the past and have had a good experience.”
Mobile FrameworkMaker says so · source ↗“The project is completely built using Expo! It greatly simplifies DX and provides awesome tooling.”
Mobile FrameworkMaker says so · source ↗“Built the iOS app in React Native and shipped it with EAS Build. One codebase, a clean path to the App Store, and to Android next.”
Mobile FrameworkMaker says so · source ↗“Expo built-in packages, incredible all in one, helped us develop quicker. Cross-platform”
Mobile FrameworkMaker says so · source ↗“Made deployment to the App Store way easier.”
Mobile FrameworkMaker says so · source ↗
React Native
Cross-platform native17 Next.js products here (31%), against 29% of all makers' products.
Best foriOS and Android apps written in React that render real native views, with full control over the native projects and build setup.
Trade-offThe React Native team recommends starting with a framework such as Expo; without one you set up native builds, signing, routing and updates yourself.
“The OG and the core fundamentals on which RapidNative is built! We are always grateful for the work by Meta, Expo and all the contributors making React Native what it is today!”
“React Native help us develop multiple platforms together.”
Mobile FrameworkMaker says so · source ↗“For building a smooth, cross-platform app experience.”
Mobile FrameworkMaker says so · source ↗“For powering our mobile app.”
Mobile FrameworkMaker says so · source ↗“The OG and the core fundamentals on which RapidNative is built! We are always grateful for the work by Meta, Expo and all the contributors making React Native what it is today!”
Mobile FrameworkMaker says so · source ↗“Building financial calculations, real-time data syncing, and complex state management once for both platforms = game changer. The component reusability meant I could maintain consistent UX while still respecting platform-specific patterns (iOS swipe gestures, Android back button, etc.). React Native made it possible for one developer to build what usually takes a team. This is the democratization of app development. 🚀”
Mobile FrameworkMaker says so · source ↗“React Native helped us build **Unlust** faster by allowing a single codebase for both Android and iOS. It gave us **native-level performance** with smooth animations, essential for our dark UI and breathing tools. With its massive ecosystem and community, we could **ship features rapidly** like Firebase auth, Lottie, and analytics without reinventing the wheel.”
Mobile FrameworkMaker says so · source ↗“Behind the scenes, the data is stored in Firebase , the frontend made using React , and the mobile app using React Native .”
Mobile FrameworkMaker says so · source ↗“The groundwork for the app, makes it quick and easy for a React developer to create native apps for both iOS and Android.”
Mobile FrameworkMaker says so · source ↗
Flutter
Cross-platform native9 Next.js products here (17%), against 34% of all makers' products.
Best forPixel-consistent UI across iOS, Android, web and desktop from one Dart codebase.
Trade-offDart is a language you'll probably use only for this, and you can't share code with a TypeScript web app.
“Thanks to Flutter for enabling rapid, efficient app development at Aupair Valley! Your framework makes innovation a breeze. #BuildFast”
“Flutter made cross-platform development effortless, allowing us to deliver a beautiful and consistent experience on both iOS and Android. Its expressive UI framework brought the vision of uList to life.”
Mobile FrameworkMaker says so · source ↗“The cross-platform desktop app is built using Flutter, and I love building apps with Flutter.”
Mobile FrameworkMaker says so · source ↗“One codebase gives native-quality iOS experience and lets us iterate quickly while we build more platforms”
Mobile FrameworkMaker says so · source ↗“Flutter is faster to develop, more flexible in design, and delivers a smooth user experience across all platforms.”
Mobile FrameworkMaker says so · source ↗“We chose Flutter for its efficiency and speed in building cross-platform apps. So far, we’ve launched on macOS and iPad, and we’re working on mobile (iPhone and Android), with Windows and Linux coming soon. Couldn't happen without Flutter!”
Mobile FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (platform firebase app)”
Mobile FrameworkMaker says so · source ↗“Thanks to Flutter for enabling rapid, efficient app development at Aupair Valley! Your framework makes innovation a breeze. #BuildFast”
Mobile FrameworkMaker says so · source ↗“Loved building on top of Flutter. We love Material Design”
Mobile FrameworkMaker says so · source ↗“Flutter is hands down one of the best tool to make a cross platform desktop app fast and efficient without sacrificing performance.”
Mobile FrameworkMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: Jetpack Compose (1).
Real options for mobile framework not seen among these Next.js products yet: Compose Multiplatform, SwiftUI, Capacitor, Ionic Framework.
Getting mobile framework right
If you already have a web app and mobile is a companion, wrap it or share code with it first. If mobile is the product, pick a cross-platform framework unless you only target iPhone. Budget time for store review, signing and push notifications — they take longer than the UI.
- Leaving store review, code signing and push notifications to the final week, when each can take days to sort out.
- Planning a feature that needs a native API without checking the framework has a maintained plugin or module for it.
- Shipping with no over-the-air update or forced-update path, so a bad release stays on users' phones until the next review passes.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for mobile framework?
Among 54 makers' products built with Next.js that we know the mobile framework of, Expo leads: 28 of them (52%), 1.4× its share among all makers' products (36%). Next come React Native (17) and Flutter (9).
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its mobile framework. How evidence is collected.