Insights

Flutter vs native for a B2B mobile app

For a B2B app the question is rarely which framework is faster in a benchmark. It is how many codebases your team will maintain for the next five years, and which device features the workflow depends on.

What is the actual difference?

A native app is written twice: Swift for iOS, Kotlin for Android, each with the platform's own UI toolkit. Flutter is one Dart codebase compiled to native machine code for both platforms, drawing its own interface with its own rendering engine. Platform features that Flutter does not expose are reached through platform channels, which are small pieces of native code you still write and maintain.

Flutter and native compared for a B2B mobile app
FlutterNative (Swift and Kotlin)
CodebasesOne, in DartTwo, one per platform
Business rulesWritten onceWritten twice and kept in agreement
InterfaceDrawn by Flutter's own engineThe platform's own UI toolkit
Platform-specific featuresThrough plugins or platform channelsDirect access
FitsOperational apps shared across iOS and AndroidProducts defined by OS or hardware features

When does Flutter fit a B2B product?

Most B2B mobile work is operational: a field worker completes a job, a driver follows a route, a manager approves a request. The screens are forms, lists, maps, scanning, and status. Those behave the same on both platforms, and one codebase means one set of business rules, one set of tests, and one release train.

RecycleOrigin is the public example. Its generator, collector, and facility clients are Flutter, on Go and Python services with PostgreSQL. Three roles share one operational record, and a rule changed once is changed for every client. The case study is on RecycleOrigin.

When is native worth two codebases?

Native is the better choice when the product is defined by something the operating system provides: deep background processing, a custom camera or audio pipeline, new OS features on release day, or tight integration with platform-specific hardware. It is also the right call when you already employ a Swift team and a Kotlin team and the app is their main product.

The cost is not only writing features twice. It is keeping two implementations of the same business rule in agreement, with two test suites and two review queues. For an operational B2B app that cost seldom buys anything the user notices.

How do we decide on a project?

In discovery we list the device capabilities the workflow needs and check each one against what Flutter supports directly and what would need a platform channel. If the list is short and standard, we recommend Flutter. If the product lives in the capabilities on that list, we say so and scope native. A mobile MVP is planned for 1–3 weeks on our mobile and web applications page; that is a planning duration, not a quote.

See mobile and web applications for scope and RecycleOrigin for the shipped example.

Sources and further reading

FAQ

Is Flutter good enough for a B2B mobile app?

Yes, when the app is mostly forms, lists, maps, scanning, and workflow screens shared across iOS and Android. One codebase keeps business rules, tests, and releases in one place.

When should a B2B app be native instead?

When the product depends on platform-specific hardware or OS features, such as heavy background processing or a custom camera pipeline, or when separate Swift and Kotlin teams already own it.

What does Reorigin use for mobile?

Flutter and Dart when one codebase fits the product, and Kotlin where native is required. RecycleOrigin's generator, collector, and facility clients are Flutter on Go and Python services.

How long does a mobile MVP take?

Reorigin's mobile and web applications page plans a mobile MVP for 1–3 weeks after discovery. That is a planning duration, not a quote.