( Guide )
Flutter or Native (Swift and Kotlin): Which Should You Build?
Flutter vs native app development: one codebase for iPhone and Android or two. Two native apps can double the build price (Clutch, 2026). When each wins.

( The Short Answer )
Build in Flutter if your app is mostly screens, forms, data and payments and must run on iPhone and Android: one Dart codebase and one team, where two native apps "will double the overall price", per Clutch (September 2026). Build native in Swift and Kotlin for heavy 3D or AR, brand-new platform features, deep background work or a one-platform app. We quote each app from its written scope, at a fixed price in writing.
Every business that needs an app on iPhone and Android hits the same fork: build it once in Flutter, or twice, in Swift for Apple and Kotlin for Android. The choice sets the budget, the team and years of upkeep, so make it on purpose.
Should you build your app in Flutter or native?
Build in Flutter if the app is mostly screens, forms, data and payments on both iPhone and Android; build native in Swift and Kotlin if it depends on heavy 3D, AR, brand-new platform features or one platform. Most business apps are the first kind, so we start in Flutter and add native code where a feature needs it.
| Flutter | Native (Swift + Kotlin) | |
|---|---|---|
| Codebases | One, in Dart, for iPhone and Android | Two: Swift for iPhone, Kotlin for Android |
| Team | One Flutter team | An iOS developer and an Android developer |
| Build cost | App code written once | Two native apps double the price, per Clutch (2026) |
| Speed | Compiled to machine code; drawn by Flutter's engine | Compiled to machine code; drawn by the system |
| Look | Flutter's own copies of the system controls | The system's own controls |
| New OS features | Once a plugin exists, or via a native module | As soon as Apple or Google ship the tools |
What is Flutter?
Flutter is Google's framework for building apps for iPhone, Android, the web and desktop from one codebase, written in the Dart language. Flutter's site describes it as "supported and used by Google".
Two details explain how it behaves. Your code is compiled ahead of time into native machine code on the phone, per Flutter's FAQ (updated September 2026), so it is not a website wrapped in an app. And Flutter does not use the phone's built-in buttons and menus: it draws every pixel with its own engine, Impeller, using its own versions of Google's Material and Apple-style "Cupertino" widgets. Flutter's Impeller page (August 2026) says Impeller is the only renderer on iOS and the default on Android from API level 29, and that it compiles its shaders before the app ever runs.
What does native app development mean?
Native means building each app in its platform maker's own language and tools: Swift and SwiftUI for iPhone, Kotlin and Jetpack Compose for Android, which makes two apps and two codebases.
Apple calls Swift its programming language for all Apple platforms and builds interfaces with SwiftUI; Google calls Jetpack Compose "Android's recommended modern toolkit for building native UI" and has said since 2019 that Android development is Kotlin-first. A native app uses the system's own controls and can use a new feature as soon as Apple or Google ship the tools. The cost is two separate products: each feature is designed once but built, tested and fixed twice, and the apps drift apart unless someone keeps them in step.
Is Flutter cheaper than building two native apps?
Usually yes: one Flutter codebase replaces two native ones, so the app code is written, tested and maintained once, while the backend, design and store work cost about the same either way.
Clutch's mobile app pricing guide, from a B2B reviews directory and updated September 2026, says one native iOS app plus one native Android app "will double the overall price", and that a hybrid app could be more cost-effective, with some limits on performance and functionality. Our view: the real multiplier is a little under two, because design and backend are shared.
The team is the other half. Native needs someone fluent in Swift and someone fluent in Kotlin; Flutter needs Dart, plus native skills for the occasional module. If you hire in-house, the Bureau of Labor Statistics puts the median software developer wage at $135,980 as of May 2025, so a second platform specialist is a six-figure decision. Price ranges are in our Flutter app cost guide; browser software is in our web app cost guide.
Will a Flutter app feel slower or less native than a Swift or Kotlin app?
For a typical business app the difference is hard to see, because Flutter runs as compiled machine code; it shows in heavy graphics, AR and controls that must match the newest system design.
- Speed. Lists, forms, maps and checkout run smoothly in either when built well. Native keeps an edge in sustained heavy graphics and anything built directly on Apple's or Google's 3D and AR frameworks.
- Look. Flutter draws close copies of the iOS and Android controls. Most users never notice, but when Apple or Google redesign their controls, a native app usually picks up the change when rebuilt with the new tools, while a Flutter app waits for Flutter's widgets or a plugin to catch up.
- Real platform pieces. Where a component must be the genuine article, such as a map or a web view, Flutter's FAQ says it can embed the platform's own view in a Flutter screen.
When is native Swift or Kotlin the better choice?
Native is the better build when the app's core value comes from the platform: heavy 3D or AR, newest Apple or Google features on launch day, deep hardware or background work, or a product that needs only one platform.
- Heavy 3D, AR or real-time graphics. When the main screen is a 3D scene or an AR view, the app lives inside Apple's and Google's frameworks, and a Flutter layer adds work rather than saving it.
- Newest platform features on day one. Flutter's Android integration docs say Flutter apps can call new Android APIs on release day, but warn: "Not all native features are supported by plugins, especially immediately after their release." If the product is built around this year's feature, you will write native code for it anyway.
- Deep hardware or background work. Continuous location tracking, long background tasks or a custom hardware device. When that is most of the app, most of the code is native already.
- One platform only. An iPad app for your staff gains nothing from cross-platform code.
When is Flutter the better choice?
Flutter is the better choice for most business apps that must be on iPhone and Android: customer apps, booking and ordering apps, field-staff tools, member apps and first versions of a new product.
- Both stores, one team. One codebase and one set of tests, and each feature reaches both stores at once.
- First versions. A first version tests whether people use the app; paying for that experiment twice makes little sense.
- Screens and data. Flutter's Android docs say most native features, including GPS and the camera, are covered by robust plugins, and its iOS docs name Apple's HealthKit as a framework reached the same way.
- A later web or desktop version. The same code can target both, though a portal people open in a browser is usually better as a web app.
Can you mix Flutter and native code in one app?
Yes: a Flutter app can call Swift and Kotlin code for the features that need the platform directly, and a native app can add Flutter screens, so the choice is rarely all or nothing.
Flutter's page on platform channels, updated November 2026, describes passing messages between Flutter and Kotlin on Android or Swift on iOS, and now recommends generated bindings such as Pigeon for new projects. The result is a small native module the Flutter app calls. We often build apps this way: Flutter for the screens and logic, native modules for device sensors, background work and platform SDKs. In reverse, Flutter's add-to-app feature imports Flutter into an existing native app as a module, so new screens are built once without a rewrite.
What does each option cost to maintain over time?
Both need yearly upkeep, because Apple and Google raise their requirements every year; a Flutter app also follows Flutter's releases, but you update one codebase instead of two.
| Who | Requirement | Date |
|---|---|---|
| Apple | Uploads must be built with Xcode 26 or later | Since April 28, 2026 |
| Google Play | New apps and updates must target Android 16 (API level 36); existing apps need Android 15 (API level 35) to stay available to new users | August 31, 2026 |
| Flutter | Four stable releases: 3.41, 3.44, 3.47 and 3.50 (November target) | 2026 |
Fall behind and the app keeps working for current users, but Apple rejects updates built with older tools and Google Play stops offering a stale app to new users on newer Android versions. With native, each change lands on two codebases. With Flutter, the Flutter upgrade comes first, then the thin iOS and Android layers; a plugin that lags a new OS can hold an update up, so keep the plugin list short.
How popular is Flutter compared with native and React Native?
Flutter led the cross-platform mobile frameworks in the last Stack Overflow survey that asked, used by 9.4% of respondents in 2024, and Google, quoting the vendor Apptopia, says it accounts for nearly 30% of new free iOS apps.
| Framework | All respondents | Professional developers |
|---|---|---|
| Flutter | 9.4% | 9.4% |
| React Native | 8.4% | 9.0% |
| SwiftUI | 4.3% | 4.3% |
The 2025 and 2026 surveys dropped that question. The 2025 survey still asked about languages: 5.9% of 31,771 respondents had worked extensively in Dart, Flutter's language, 5.4% in Swift and 10.8% in Kotlin.
The app-store share is a vendor number. Google's I/O 2025 post (May 21, 2025) cites Apptopia, an app-intelligence firm, for nearly 30% of new free iOS apps; Flutter's iOS page gives 28% for 2024. Google makes Flutter, neither page explains Apptopia's method, and it counts free apps only, so read it as a sign of wide use, not a market share.
Where does React Native fit?
React Native is the other main cross-platform option: the app is written in JavaScript and React and, in its own words, "rendered with native code", which suits teams that already build in React. The Flutter-or-native questions here apply to it in much the same way. Flutter is our default for a new app, and we build in React Native for teams that already work in React.
How do you decide between Flutter and native for your app?
Work through these in order; if no native trigger applies, build in Flutter, and if one applies to a single feature, build in Flutter with a native module for it.
- Does version one need both iPhone and Android? If only one platform matters, build native for it.
- Is the core 3D, AR or real-time graphics? Build native.
- Does it depend on a feature Apple or Google announced this year? Check for a Flutter plugin; if none, plan a native module, or a native app if that feature is the product.
- Does it run long in the background or talk to custom hardware? Plan native modules; if that is most of the app, build native.
- Do you already have a native app and team? Extend it, and consider add-to-app for new screens.
- Who maintains it? Every year of updates lands on one codebase or two.
- Is the scope written screen by screen? That is what makes a fixed price possible; see our hourly vs fixed price guide.
Whoever builds it, settle first who owns the repository and the Apple and Google developer accounts; our website ownership guide lists the contract clause to look for.
What does American Web Guild charge for a Flutter app?
We do not publish a price for apps: each one is quoted from its written scope, as a fixed price in writing within 24 hours, and never billed by the hour. The screens and user roles, the backend, the device features, offline use and any native modules set the price. Send the scope through the form to get yours.
We build in Flutter first and add native Swift or Kotlin modules where a feature needs the platform. The backend runs on Firebase, Supabase or a Node.js API in your own accounts; working builds reach your phones through TestFlight and Google Play internal testing at each milestone; and the apps are submitted from your own Apple Developer and Google Play Console accounts. Details are on our Flutter app development page.
You own the design, the custom code and the content once the final invoice is paid, which falls due before launch, and the domain, hosting and platform accounts are in your name from the start. The repository sits in your GitHub or GitLab account from the first commit.
The limits, plainly. Store fees are yours: as of November 2026 the Apple Developer Program costs $99 a year and Google Play a one-time $25, and Apple and Google take their commissions on paid apps and in-app purchases. Hosting and API fees are billed in your name, and a care plan after launch is priced separately. If the app is built around heavy 3D, AR or one platform's newest features, fully native Swift or Kotlin is the better build, and we will say so in the scope. Live App Store and Google Play examples are shown on a call.
Frequently asked questions
- Is Flutter good for iPhone apps?
- Yes, for most business apps. On iOS, Flutter compiles your code to native ARM machine code (Flutter FAQ) and draws with Impeller, the only renderer it supports there (Impeller docs, August 2026). Google, quoting the vendor Apptopia, says Flutter accounts for nearly 30% of new free iOS apps. Native Swift still wins for heavy 3D, AR and Apple features on launch day.
- Does building native cost twice as much as Flutter?
- Close to it for the app itself. Clutch's mobile app pricing guide, updated September 2026, says a native iOS app plus a native Android app will double the price. Shared design, backend and store work bring the real multiplier a little under two, and the yearly OS updates land on two codebases instead of one.
- Can a Flutter app use the camera, GPS or Apple Health?
- Yes. Flutter's docs say most native features, including the camera and GPS, are covered by plugins, and its iOS docs name HealthKit as an Apple framework reached the same way. Where no plugin exists, the app calls a small native Swift or Kotlin module through platform channels or generated bindings such as Pigeon.
- Will Google drop Flutter?
- No one outside Google can promise either way. The signs point to continued investment: flutter.dev describes it as supported and used by Google, and its published schedule lists four stable releases in 2026. Native modules in a Flutter app are ordinary Swift and Kotlin, and the code is yours, so a move to native later stays possible.
- Can I start in Flutter and switch to native later?
- Yes. The backend, the designs and the store listings carry over, and a native rewrite can be done one platform at a time. Often it is not needed: adding native modules for the features that outgrow Flutter usually costs less than rebuilding. Flutter's add-to-app also lets native and Flutter screens live in one app during a move.
- Is React Native better than Flutter?
- Neither is better across the board. React Native renders with the platform's own controls and suits teams that already work in React; Flutter draws its own interface and was slightly more used in the Stack Overflow Developer Survey 2024, 9.4% of respondents against 8.4%. Both allow native modules. Flutter is our default for a new app; we build in React Native for teams already in React.



















