Opinion
Which Cross-Platform Mobile Framework Should I Use in 2026?
June 22, 2026
There's no single best cross-platform framework in 2026, and anyone who tells you otherwise is selling something. The honest answer is a decision: match the framework to your team's skills, the kind of app you're building, how much performance you actually need, and whether you also need the web. Get those four right and most of the shortlist falls away on its own.
I'm Gareth, CTO at Foresight Mobile. We build mostly in Flutter, so you know my leanings, but this only helps you if it's straight about where the others win. The field has changed a lot since the older version of this post: one framework on that list is now dead, another has gone from also-ran to serious contender, and a couple of "dying" options have quietly come back. Let me walk you through the 2026 shortlist and then how to pick.
Six names matter in 2026. Here's what each one is actually for now.
Flutter is now the second most popular app-development toolkit on both the App Store and Google Play, used by around 1.5 million developers, up roughly 50% in a year. The current release is Flutter 3.44 with Dart 3.12, from Google I/O in May 2026. It renders every pixel itself (through Impeller, which replaced the old Skia engine on Android this year), so a design looks identical on every device and holds a smooth frame rate. One codebase covers iOS, Android and the web. It's our default for new consumer-facing, design-led apps, and I'll explain why below.
React Native is JavaScript, the language most web teams already use, and it plugs into the enormous npm ecosystem. The big 2026 update: its old "bridge", long the main complaint against it, is gone. The New Architecture (Fabric and JSI) is the default, and the legacy bridge was removed entirely in version 0.82. Most new projects go through Expo, which around 83% of recent builds now use. If you already have React developers, this is the fastest, cheapest way onto mobile.
This is the field's biggest mover. Professional-developer use more than doubled in a year, from 7% to 18%, per JetBrains. The reason: Compose Multiplatform for iOS became production-ready in May 2025, so Kotlin Multiplatform can now share the UI across iOS and Android, not just the business logic underneath. Netflix, McDonald's, Cash App, Forbes and Duolingo run it in production. It suits teams who already write Kotlin and want a native feel with shared code. The trade-offs are a smaller talent pool and newer iOS-UI tooling than Flutter's.
Written off a few years ago, web-on-mobile has come back. Capacitor 7 shipped in January 2025 and Capacitor 8 is already announced. The draw is that you build with standard web frameworks like React or Next.js and ship the same code to native. It renders in a WebView, so it's a strong fit for content, forms, dashboards and line-of-business apps, and a poor fit for graphics-heavy or animation-heavy consumer apps where smoothness matters.
The honest question mark. Xamarin, which the older version of this post still listed, reached end of support in May 2024, and MAUI is its successor. It ships with .NET 10, but its support window is much shorter than the rest of .NET (roughly six months after the next major version, against a three-year window elsewhere), and 2026 releases have been regression-heavy. It's defensible if your team already lives in C# and .NET. For anyone else, it's the hardest of the six to recommend.
A PWA is the cheapest way to reach every platform from one web codebase, and web push has worked on iPhone since iOS 16.4. The caveats are real, though: on iOS, push only works if the user adds the PWA to their Home Screen, which far fewer people do, and in the EU, Apple removed standalone PWA support under the Digital Markets Act. Great for reach and low-commitment products. Not a replacement for an installed app when you need reliable notifications, offline reliability or deep hardware access.
Ignore the league tables for a moment. Four questions decide this more reliably than any popularity chart.
What team do you already have? This is the biggest single factor. A React or JavaScript team ships fastest on React Native or Capacitor because the skills transfer immediately. An existing native iOS and Android team that wants to share code without a full rewrite is a natural fit for Kotlin Multiplatform. A .NET shop has a reason to look at MAUI. Starting fresh, with no constraint, and wanting one team to cover everything points to Flutter.
What kind of app is it? A design-led, animation-heavy, brand-consistent consumer app wants a toolkit that controls its own rendering, which means Flutter or fully native. Content, forms, dashboards and internal business apps are comfortable territory for Capacitor or Ionic. An app where each platform must feel completely native, with shared logic underneath, suits Kotlin Multiplatform.
How much performance do you really need? Be honest here. If you're building 120fps animation, games or heavy graphics, a WebView-based option won't cut it; you want Flutter or native. If it's a standard CRUD or business app, frankly any of these will be fast enough, and performance shouldn't be the deciding vote.
Do you need the web too? If the same app has to run on the web from one codebase, that narrows things quickly to Flutter (which has a web target) or the web-native options like Capacitor and PWAs. This is the branch where our piece on building for mobile and web from a single codebase goes deeper.
For most UK businesses building a new, design-led, customer-facing app, often one that also needs to work on the web, Flutter app development is our default. One codebase covers iOS, Android and web with a consistent, high-performance UI, and the long-term hiring and maintenance cost tends to be lower than running separate native teams. That's the case I make in more detail in why Flutter outperforms the competition.
But "our default" isn't "your answer". We build in React Native too, and the right pick genuinely depends on the four questions above. If you'd rather not gamble six figures on getting that call right, our App Gameplan settles it properly: in four weeks, for a fixed fee, you get a board-ready recommendation on the stack that fits your product, your team and your budget, before a line of production code is written. Or get in touch and we'll talk it through.
One last thing on reading popularity stats: they move every year and each survey samples a different crowd, so treat them as direction, not gospel. The signals that actually matter are duller and more reliable. Is the framework's vendor still shipping releases? Are its big dependencies maintained? Are serious companies betting production apps on it? Answer those three and you'll avoid backing the wrong horse.
What's the best cross-platform framework in 2026?
There isn't one. Flutter and React Native are the two most widely used, and Flutter is our default for design-led consumer apps because it renders its own UI consistently across devices. But the best choice depends on your team's existing skills, the type of app, your performance needs, and whether you also need the web.
Is Xamarin still an option?
No. Xamarin reached end of support in May 2024. Its successor is .NET MAUI, which is worth considering only if your team already works in C# and .NET, and even then the shorter support window is a real planning consideration.
Is Kotlin Multiplatform ready for production?
Yes. Compose Multiplatform for iOS became production-ready in May 2025, and companies like Netflix, McDonald's and Duolingo run Kotlin Multiplatform in production. It's strongest for teams who already write Kotlin and want shared code with a native feel.
Are PWAs good enough instead of a native app?
For reach and low-commitment products, yes. For anything that depends on reliable push notifications, offline use or deep device features, no, especially on iOS where push needs the user to add the PWA to their Home Screen, and where the EU has its own restrictions.
Which framework is cheapest to build with?
The cheapest is usually the one your existing team already knows, because you avoid hiring and retraining. If you're starting fresh, a single cross-platform codebase (rather than two native apps) avoids paying for the most expensive phase twice. We cover real numbers in our guide to how much it costs to build an app.
