Native vs cross-platform: which app should you build?
Native, cross-platform, or web-based? A decision guide on device access, performance, team, maintenance burden, and store rules, with verified 2026 facts.

For most business apps, cross-platform is the right default. React Native and Flutter have both been in serious production use for most of a decade, they ship apps that ordinary users cannot distinguish from native, and they leave you one codebase to maintain instead of two. Native is still the correct answer for a specific and fairly narrow set of apps: games and graphics engines, real-time camera or augmented reality work, heavy background processing, deep platform integration, and anything that has to use a brand-new iOS or Android capability the week it launches.
If your app is a booking tool, a client portal, a scheduling app for field staff, a member app, or a store, that list does not describe you. I have been building software from one office in Edina for 14 years, and the framework decision almost never determines whether an app succeeds. Scope discipline does. This post is about making the framework decision quickly and correctly so you can get back to scope.
One note on what this post is not. It is not a cost guide. Every market figure for apps, with its source, is in how much it costs to build an app, and the one short cost section below points there rather than repeating it.
What is the difference between native, cross-platform, and web-based apps?
There are three families, and it helps to be precise about what each one actually is.
Native means writing the app twice, in each platform’s own language and tools. iOS in Swift with SwiftUI, built in Xcode. Android in Kotlin with Jetpack Compose, built in Android Studio. Two codebases, usually two developers or two teams, one product.
Cross-platform means one codebase that runs on both platforms. React Native is written in JavaScript, and its homepage puts the mechanism plainly: React primitives render to native platform UI, so a React Native button is the platform’s own button. Its New Architecture, a rewritten renderer and native bridge, has been the default since version 0.76 shipped in October 2024. Flutter is Google’s framework, written in Dart, and it draws every pixel itself rather than using platform controls, which is why a Flutter app looks identical on both platforms whether or not you want it to. Flutter’s documentation, read in November 2026, says its Impeller rendering engine has been the default on iOS and on Android API 29 and up since release 3.27, and the only supported engine on iOS. Kotlin Multiplatform is the third option: it shares business logic across platforms while leaving the interface native on each side, and JetBrains’ Compose Multiplatform adds a shared UI on top. The Compose Multiplatform site, read in November 2026, lists Android, iOS, and desktop as stable and web as beta.
Web-based means the app is a website inside a native shell, or no shell at all. Capacitor, from the Ionic team, is the current standard for the shell. Its documentation describes it as a cross-platform native runtime that wraps a web app in a native container for iOS and Android, with a plugin API in Swift, Java, and JavaScript for reaching the camera, GPS, push, and the rest. A progressive web app, or PWA, skips the shell and the store completely: it is a website the user installs to their home screen.
If any of those terms are new, the glossary has plain-language definitions for most of them, and web app vs website vs mobile app explains the category lines.
How do the three approaches compare?
| Native (Swift + Kotlin) | Cross-platform (React Native, Flutter, Kotlin Multiplatform) | Web-based (Capacitor, PWA) | |
|---|---|---|---|
| Codebases to maintain | Two | One, with small native modules where needed | One, shared with your website |
| Performance ceiling | Highest. Matters for games, 3D, video processing | Very good. Indistinguishable for lists, forms, maps, media playback | Adequate for content and forms. Noticeable on heavy animation |
| Device features | Everything, on day one | Nearly everything through plugins. Unusual hardware may need native code | Common features only. iOS restricts background work |
| Look and feel | Platform-correct by default | React Native uses platform controls. Flutter draws its own, consistent everywhere | Feels like a website unless carefully designed |
| Team you need | An iOS developer and an Android developer | One mobile team. Web developers transfer to React Native readily | Your existing web developers |
| Yearly OS-upgrade work | Two platforms to retest and fix each fall | One codebase to retest, one dependency tree | Mostly the same work as your website |
| Shipping a fix | Store review for every change | Store review; JavaScript-layer fixes can ship over the air within Apple’s limits | Instant for web content. Store review only for shell changes |
| App store | Fully accepted | Fully accepted | Capacitor accepted if the app does real app things. PWA needs no store |
Two notes on that table. First, over-the-air updates are a genuine operational advantage of React Native and Capacitor: a copy fix or a small bug fix in the JavaScript layer can reach users the same day without waiting for review. Apple permits this within limits, and the limit is roughly that you cannot change what the app fundamentally is between reviews. Do not build a business plan around dodging review.
Second, review itself is faster than its reputation. Apple’s App Review page, read in November 2026, says it typically reviews at least 50 percent of submissions in under 24 hours and 90 percent in under 48. The delays that hurt projects come from rejections, not queue time, and the common rejections are covered below.
Does your app need the device, or just a screen?
This is the first real question, and it decides most cases on its own.
Write down every hardware or platform feature the app needs, then sort them into three piles. The first pile is what a browser does fine: forms, lists, photos from the camera roll, a single photo capture, location while the app is open, payments through a hosted checkout. If everything is in this pile, you are looking at a web app or a PWA, and you should read website or app before you spend anything.
The second pile is what cross-platform plugins handle well: push notifications, biometrics for sign-in, barcode scanning, Bluetooth to a known device, offline storage with sync, background location for the duration of a shift, in-app payments through the store. Both React Native and Flutter have maintained plugins for each of these. If your list lives in this pile, cross-platform is the default.
The third pile is where native earns its cost: real-time camera processing, augmented reality, audio pipelines that run while the app is closed, home screen widgets, watch apps, CarPlay or Android Auto, share extensions, and anything Apple or Google announced at this year’s developer conference that you need in production this year. One item from this pile can usually be built as a native module inside a shared codebase. Five items means the shared codebase has stopped paying for itself.
When should you build native instead?
Five cases, and they are real.
- Games and heavy graphics. If you are rendering a 3D scene or running a physics loop, use a game engine or go native. Do not use a business app framework for this.
- Intensive camera, video, or AR. Real-time filters, on-device computer vision, document scanning with custom processing, ARKit or ARCore experiences. Taking a photo is easy anywhere; processing 60 frames a second is not.
- Serious background processing. Continuous location tracking, background audio pipelines, large sync jobs that must run while the app is closed. Both platforms restrict this heavily, and the escape hatches are native.
- Deep platform integration. Home screen widgets, watch apps, Siri or Assistant integration, CarPlay, complex share extensions. Some of this is possible with a native module bolted onto a shared codebase, but if there are five such features, the shared codebase stops paying for itself.
- Day-one adoption of new OS features. If your product has to demo the newest iOS capability during the same keynote week, native is the only route.
Notice what is not on that list: “we want it to feel premium.” Feel is a design and performance-tuning outcome. A well-built React Native app beats a badly built native one every time, and users cannot tell which framework rendered the list they are scrolling.
What team can you actually hire and keep?
The framework you can staff beats the framework that benchmarks best.
If your developers, or the shop you are hiring, already write JavaScript or TypeScript for your website, React Native is the shortest path, and a lot of logic can be shared with a web app. If your Android team already writes Kotlin, Kotlin Multiplatform lets them bring iOS along without hiring a Swift team. If you are hiring from scratch and want one codebase with one look everywhere, Flutter’s Dart is a small language to learn and its tooling is mature.
Native needs two skill sets, and in a small market that means two freelancers or an agency with both on staff. When one leaves, half your app has no owner. That is the real staffing risk of native for a small organization, and it matters more than any performance number.
One caveat the other direction: cross-platform is one codebase, not zero platform knowledge. You still need someone who understands App Store review, provisioning profiles, Play Console releases, and how push notifications differ on each side. A team that has only ever built websites will lose weeks learning that, so ask any shop you are considering how many apps they have actually shipped to both stores.
What does the second codebase cost you every year?
This is the question people skip, and it is the one that quietly decides the whole thing.
Two native codebases do not cost twice as much to build, because design, backend and API work, content, test plans, and project management are shared regardless of approach. What genuinely doubles is the client-side engineering, and that is a large share of the project.
The maintenance line doubles more cleanly. Apple and Google each ship a major OS release every fall, and both require apps to keep up. Google Play’s target API policy, read in November 2026, requires new apps and updates to target Android 16 (API level 36) from August 31, 2026, with extensions available to November 1, 2026, and the requirement moves up every year. Apple periodically requires new submissions to be built against a recent SDK. With one codebase that is one round of testing and fixing a year. With two it is two, forever, and when a dependency breaks on one platform you fix it twice.
For the percentage the guides use for yearly app maintenance, with their names and dates, see the maintenance section of the app cost post. The point here is simpler: whatever that number is for one codebase, it is roughly double for two.
What do the store rules change?
More than most first-time app owners expect, and none of it depends on the framework.
Apple’s App Store Review Guidelines, read in November 2026, include three rules that hit small-organization apps most often. Guideline 4.2, minimum functionality, says an app should include features, content, and UI that elevate it beyond a repackaged website, and that an app that is not particularly useful, unique, or app-like does not belong on the App Store. This is the rule that makes “just turn our website into an app” a non-project, and it applies to a Capacitor shell exactly as much as to a native build. Guideline 5.1.1 says that if your app supports account creation, you must also offer account deletion within the app. Guideline 3.1.1 says that unlocking features or content inside the app, including subscriptions and premium content, must go through in-app purchase. Apple’s Small Business Program page lists a reduced 15 percent commission for developers under one million dollars in prior-year proceeds, and the standard rate otherwise. Physical goods and real-world services booked through an app are treated differently from digital goods, so check which side of that line you are on before the business model is set.
Google Play has its own gates. Its help page on testing requirements, read in November 2026, says a personal developer account created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for 14 consecutive days before it can apply for production access. That requirement alone has pushed launches back a month for people who found out about it the week they wanted to ship. Both stores require privacy disclosures, Apple as privacy labels and Google as the data safety section, and both must accurately describe what you collect.
And the fees, from the store pages read in November 2026: Apple’s Developer Program is a $99 annual membership, and a Google Play developer account is a one-time $25 registration fee.
None of this is a reason to pick one framework over another. It is a reason to budget two to four weeks of calendar slack between “the app is done” and “the app is public,” whichever you pick, and how to build an app for your business walks through that submission phase step by step.
Which should you build for your type of app?
| App type | Recommended | Why |
|---|---|---|
| Client portal or member app | Cross-platform, or a web app | Forms, lists, and auth. Nothing here needs native |
| Home care or field staff scheduling | Cross-platform, or buy it | Offline data and GPS check-in are solved problems, and Minnesota’s state EVV system already exists |
| Clinic or therapy practice app | Cross-platform | Intake and messaging. Spend the budget on security instead |
| School or district app | Cross-platform, or none | Often a mobile-friendly website plus push does the job |
| Nonprofit donor or volunteer app | Usually none | A good website converts better and is found on Google |
| Online store companion app | Your platform’s own app | Shopify and similar already offer one |
| Booking and payments for a service business | Cross-platform | The store payment rules matter more than the framework |
| Photo, video, or scanning product | Native, or hybrid with native modules | Real-time processing is the whole product |
| Game or 3D experience | Game engine or native | Wrong tool otherwise |
| Delivery or dispatch with constant tracking | Native, or cross-platform with a native location module | Background location is the hard part |
| Internal tool used on company devices | Web app or Capacitor | No store, no review, cheapest path |
Should you build a web app or a PWA instead?
Often, yes, and this is the option most people skip past too quickly.
If your users are on a computer as much as a phone, or if you need people to reach the tool from a link without installing anything, a web application is cheaper to run, has no store, and updates instantly for everyone. A lot of what people describe as an app idea is really a portal, and web app vs website vs mobile app is worth ten minutes before you commit a budget.
Progressive web apps deserve a fair hearing too. On Android a PWA installs to the home screen, works offline, and sends push notifications. On iOS the story is narrower. Apple’s WebKit team announced web push for home screen web apps in iOS 16.4 in February 2023, but it only works after the user adds the app to the home screen from Safari, background processing stays limited, and you get no App Store listing. If discovery through the store is part of your plan, a PWA is not enough. If your users are staff or existing clients you can show how to install it, it may be plenty, and Capacitor gives you a store listing later without a rewrite.
How much does the framework decision change the cost?
Less than the scope decision, and I will keep this short because the full picture lives elsewhere.
The cost guides collected in how much it costs to build an app price a focused mobile MVP in the tens of thousands of dollars and most small-business apps well above that, and every one of those guides assumes a single shared codebase. Going native on both platforms adds the second client build on top. Going web-based removes the store, the second platform, and most of the yearly OS work. Within any one of those three approaches, the number of user roles, the integrations, and how much you insist on building before you have a single user move the price far more than the framework does.
So decide the framework from the sections above, in an afternoon, and spend the real effort on scope. That post has the figures, with their sources and read dates; this one has already said what it needs to about money.
What to do next
List every device feature the app needs and sort it into the three piles above. If everything is in the first pile, read website or app and consider not building an app. If the list lives in the second pile, cross-platform is your default, and the choice between React Native, Flutter, and Kotlin Multiplatform should follow the team you can hire. If three or more items are in the third pile, budget for native and find a shop that ships that kind of app every day; if what you need is a game, an AR product, or a real-time video pipeline, that shop is not us, and we will say so on the first call.
If you want a second pair of eyes on which pile your list is in, tell us what you are working on. TayoPro builds mobile apps cross-platform from a single codebase, with native modules where a feature requires them, and web applications when the phone is not the point. We also design and build websites and keep them maintained month to month, all at a fixed price quoted in writing, and we will tell you plainly if you do not need any of it.
FAQ
Questions people ask about this
Is React Native or Flutter better in 2026?
Both are production-grade and either will serve a normal business app. Pick React Native if your team already writes JavaScript or TypeScript, or if you want to share logic with a web app; its primitives render to the platform's own native UI components. Pick Flutter if pixel-identical design across both platforms matters or the app is animation-heavy; it draws every pixel itself through its Impeller engine. The bigger risk is the developer you hire, not the framework.
Do cross-platform apps get rejected by the App Store?
Not for being cross-platform. Apple and Google both accept apps built with React Native, Flutter, Capacitor, and similar tools. What gets rejected is an app that fails Apple's guideline 4.2 by being a repackaged website with nothing app-like about it, one that lets people create an account but not delete it in-app under guideline 5.1.1, or one that unlocks digital content outside in-app purchase under guideline 3.1.1.
Can a cross-platform app use the camera, GPS, and push notifications?
Yes. Camera, GPS, push notifications, biometrics, Bluetooth, file storage, offline data, and payments are all well supported through maintained plugins in both React Native and Flutter. Where it gets harder is unusual or very new hardware, deep widget and watch integration, and real-time video or audio processing, which often need a small piece of native code alongside the shared code.
What is the difference between a PWA and a native app?
A progressive web app is a website that can be installed to the home screen and work offline. It needs no app store, no download, and no store fees, and you update it by publishing. A native app is installed from the store and gets full access to the device. On Android a PWA is close to an app. On iOS it is more limited: Apple added web push for home screen web apps in iOS 16.4 in 2023, but only after the user adds the app from Safari, and background work stays restricted.
Can I start cross-platform and move to native later?
Yes, and it is a reasonable plan. Most teams that do this rewrite one screen or one feature natively rather than the whole app, since React Native, Flutter, and Kotlin Multiplatform all let native code live alongside shared code. A full rewrite is a real project, so treat the first build as something you will keep for at least three years.
What is Kotlin Multiplatform and when does it make sense?
Kotlin Multiplatform shares business logic, meaning data models, networking, and rules, across Android and iOS while each platform keeps its own native interface. JetBrains' Compose Multiplatform adds a shared UI on top, and its site, read in November 2026, lists Android, iOS, and desktop as stable with web in beta. It makes the most sense for teams that already write Kotlin for Android and want to bring iOS along without a second team.
Keep reading
App Development18 min readComplete guide
How much does it cost to build an app in 2026?
A focused mobile MVP runs $15,000 to $60,000 and most small-business apps $50,000 to $120,000 in named 2026 guides. The breakdown by phase, type, and team.
App Development11 min read
Website or app? How to decide
Most organizations do not need an app. Five tests tell you whether yours does, plus an honest comparison of cost, timeline, and upkeep.
App Development13 min read
Web app vs website vs mobile app: the difference
A website informs, a web app does work in a browser, a mobile app installs on a phone. Sourced market costs, timelines, and which one you need.


