Techoship

Flutter · Native apps · Planning

Flutter or native? How we choose for each project

Flutter or native Swift and Kotlin? The questions we ask before choosing, with real examples from apps we've shipped, what each choice costs, and when we use both.

Techoship LLC · November 20, 2026 · 3 min read

"Should we build in Flutter or go native?" is usually the second question a founder asks, right after "what will it cost?". The honest answer is that it depends on a few specific things about your app, and you can work them out before anyone writes a line of code.

Here is how we decide, with examples from apps we have built.

Start with Flutter, unless something rules it out

Flutter builds an iOS app and an Android app from one codebase. For most products that means less to build, less to test and less to maintain. That is why our Flutter apps start from $6,000, while native apps for both platforms start from $12,000.

Most of what founders build fits Flutter comfortably. Firnela, a hospitality staffing marketplace, is a Flutter app with 94 screens on a NestJS backend. Heyday City Guides, a venue discovery platform, is Flutter with maps and location. Our own app Focusara even runs a language model on the phone from Flutter.

So the real question is not "is Flutter good enough?" It is "does anything in this app rule it out?"

What pushes us towards native

A hardware SDK that only exists natively. In our campus safety project, a pilot dispatches a drone to escort a student home. The drone maker's SDK is native, so the pilot app is written in Kotlin, while the student app is Flutter.

A platform feature with no good Flutter package. Our AI project management app turns speech into tasks in Arabic and English. No Flutter package did the speech part well enough, so about 1,000 lines of it are native Kotlin and Swift, inside an otherwise Flutter app.

Hardware on the phone itself. Apps built around NFC, Bluetooth devices or deep camera work spend most of their time talking to the operating system. Our NFC business card app is native for that reason.

Your client or team already works natively. If there is an existing native app, or an in-house team that will maintain it in Swift and Kotlin, matching them is often worth more than one codebase.

What native really costs

Native means two apps. Our AI interior redesign app was built natively for iOS in Swift and for Android in Kotlin. Both had to send exactly the same instructions to the AI, so we re-implemented a Swift text behaviour by hand in Kotlin to make the two apps produce byte-identical prompts.

That kind of work is what you pay for twice with native: every feature, every fix and every edge case, once per platform.

The middle path most apps should consider

The choice is not all or nothing. Flutter for the screens, plus a small native module for the one thing that needs it, gets you most of the savings and none of the limits. The AI project management app above works exactly like that: Flutter everywhere except the speech engine.

A quick way to decide

  • Choose Flutter if your app is mostly screens, forms, lists, maps, payments and notifications, and you want iOS and Android at the same time.
  • Plan a native module if one feature depends on hardware or an SDK that only exists natively.
  • Go fully native if most of the app is that kind of feature, or if a native team will own it.

Not sure which side your idea falls on? That is exactly what a one-week validation sprint answers, and the cost calculator shows the price difference for your features in two minutes.

Planning something similar?

A free consultation, then a written plan and a fixed quote.