Flutter development in Gothenburg — one codebase for iOS and Android

Intunio is a design and development studio in Gothenburg. When an app needs to reach both iOS and Android with one team, one design foundation, and a shared release cadence, Flutter is often the right call — and a framework we've shipped several products with.

Flutter development here is part of our app development: the same way of working, where designers and engineers share the backlog, but focused on when and how one codebase ships to two platforms without feeling like a compromise.

When Flutter is the right call

The platform choice is often the most consequential decision in an app project. Flutter fits when speed, a shared design foundation, and one codebase outweigh perfect platform-specific feel:

• You need to reach both iOS and Android but don't want to maintain two separate codebases and two teams.

• Design is load-bearing — Flutter renders its own UI, giving pixel-exact control and an identical expression on both platforms.

• Release cadence and iteration matter — hot reload and a mature component toolkit let design and function develop quickly and in parallel.

• The product has complex, custom interactions (animations, real-time views, graphics) where Flutter's rendering model is a strength.

Flutter is less right when large parts of the product are pure native platform functionality, or when an existing web team already lives in React — then we look at native or React Native instead. How the choice is made in practice is covered in Native vs. cross-platform.

AI has shifted the calculus toward native. When even native development becomes efficient with AI tools, the old time savings of a shared codebase shrink, so for new apps we increasingly land on native — because it delivers the best result. Flutter is still right when speed and a shared design foundation matter most.

What Flutter is good at

• One codebase, two platforms. Shared logic, shared components, and a common design foundation — without losing the platform feel where it counts.

• Its own UI toolkit. Flutter draws its own components, giving full control over the expression and making a design system directly translatable to code.

• Fast iteration. Hot reload shortens the loop between a design decision and a working interface — valuable when design and engineering work in parallel.

• Embedded targets. We've used Flutter beyond mobile, on embedded screens where it's one of the few realistic options — relevant for connected products and vehicles.

• Strong performance for animation- and interaction-heavy interfaces.

What we've built in Flutter

A few of the products we've built in Flutter:

• Swanholm Technology — companion app for a smart safety vest. We rebuilt the app in Flutter for iOS and Android as it scaled, with Bluetooth integration and AI-controlled alert features tied to the hardware.

• RGNT Motorcycles — companion app for Swedish electric motorcycles, a cross-platform update in Flutter with extended mapping (HERE) and an improved dashboard.

Both are cases where the app is the interface to a connected, physical product — one of the situations where a single codebase and tight hardware integration have to coexist.

How we work

A Flutter project follows the same setup as our app development: pre-study, design and technical foundation, sprint-based development, release and maintenance — with designers and engineers in the same team. We often start with a pre-study that lands scope, architecture, and whether Flutter really is the right call before a line of code is written. The design system is built into the foundation, which Flutter suits particularly well since the UI is rendered by the framework itself.

What does Flutter development cost?

The hourly rate is 995 SEK/h (our best price, with Team retainer), the same model as for all our app development. AI tools (Claude, Cursor, Codex) are included in the rate. See the app development packages for hours and prices — they apply here too.