Skip to content
Engineering16 Jun 20266 min read

Flutter or native: the five questions that decide it

The answer is not a preference. It falls out of hardware access, team composition, release cadence, longevity and the design bar.

We build in Swift, Kotlin, Flutter and React Native, which means we have no framework to defend. The choice comes down to five questions.

1. What hardware do you touch? Background location, BLE peripherals with custom protocols, camera pipelines, HealthKit — every one of these pushes toward native. Flutter can bridge to platform channels, but you are then maintaining native code anyway.

2. Who maintains it in three years? If your in-house team knows Kotlin, shipping Flutter creates a dependency on us that neither of us should want.

3. How often do you release? A shared codebase halves release coordination. For a product shipping weekly on both stores, that is a real ongoing saving.

4. How long will this app live? Framework risk compounds. A five-year horizon favours the platform SDKs; an eighteen-month campaign app does not.

5. How closely must you match platform conventions? Flutter draws its own widgets. It can be made to look native, but a design that must feel exactly like iOS will fight the framework.

Our default

Three or more "native" answers means native. Otherwise Flutter, and we say so in writing with the reasoning attached, so the decision can be revisited when the constraints change.

Tell us what you are building

Send a brief and a solution architect replies within one business day — with questions, not with a template.