Flutter app development
Build Flutter apps for mobile, web and desktopfrom a single Dart codebase
You want one app with one look on every device, or you have a Flutter app that needs carrying forward. Flutter draws its own interface and compiles one Dart codebase for iOS, Android, Windows, macOS, Linux and the web. Sharing that code is useful, but it does not remove platform work. Here is how we run a Flutter project, and where we would steer you towards something else.
What Flutter work covers
The jobs a Flutter engagement is normally made of.
New apps for iOS and Android
One Dart codebase with a shared design, followed by separate store submissions, signing and review for each platform.
Flutter inside an existing native app
Flutter's add-to-app route lets a new feature be written in Flutter while the rest of the app stays in Swift or Kotlin, which suits a gradual change.
Native plugins
Where a device feature has no maintained package, we write the native side and connect it through platform channels, using Pigeon to generate type-safe messaging rather than matching strings by hand.
Upgrading an older Flutter app
Bringing an app forward through breaking changes such as the UIScene lifecycle on iOS and built-in Kotlin on Android, then checking its plugins one by one.
Flutter facts as of October 2026
Taken from the Flutter documentation, because they decide who can run your app.
Current release: Flutter 3.47
Released on 12 August 2026, after 3.44 in May and 3.41 in February. A release every few months means an app left alone falls behind quickly.
Minimum devices
Flutter 3.47 supports Android API 24 and iOS 15 upwards. Android 23 and iOS 14 are out, so check your analytics before committing. Support for Intel Macs is being phased out.
Rendering
Impeller is the only rendering engine on iOS and the default on Android API 29 and above. Older or non-Vulkan Android devices fall back to OpenGL, so they need testing separately.
When Flutter is right, and when it isn't
The decision that matters most, and the one worth making before any design work.
A good fit
A branded interface that should look the same on both phones, a team that wants one codebase, and an app that behaves like an application rather than a document.
A poor fit for public web pages
Flutter's own documentation says it is not suitable for static, text-rich sites, and that its web output doesn't align with what search engines need. Keep landing pages in HTML and use Flutter for the app behind them.
Web support has limits
The WebAssembly build is listed for Chrome and Edge only. Firefox and Safari get the JavaScript build, so a web version needs its own performance test in each browser.
If your team already writes JavaScript
Dart is another language to hire for and maintain. If your web team is in React, React Native may keep more of your people and code working together.
How a Flutter project runs
Device and store questions come first, because they are the expensive ones to change later.
List the device features
Camera, notifications, background work, payments, offline use. For each we check for a maintained package, or plan a native plugin.
Set the minimum versions
We compare Flutter's supported range with your real audience, and agree which devices we will test on.
Test builds on real phones
You install test builds through TestFlight and Google Play's testing tracks, rather than reviewing screenshots.
Store submission and handover
We handle both store reviews with you, under your developer accounts, and document how to build, sign and release the app.
How we charge for Flutter work
Fixed scope suits a clear brief. Ongoing time suits an app that keeps changing.
An app with a settled feature list can be quoted as a fixed scope once the device features have been checked. If the product is still changing, or you only need Flutter developers alongside your own team, our dedicated developer model fits better. Hourly work starts from $20/h in USD, invoiced in USD, GBP, EUR or INR.
We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. In the shared hours, your product owner and our Flutter developers can test a build and talk it through. The API behind the app is often the larger part of the work, and we can build that too, for example with Laravel or Node.js.
Why no Flutter projects are named here
Most of our work is delivered under NDA, so many projects cannot be named.
That is why this page explains our approach to Flutter rather than listing apps. Our published portfolio includes no Flutter app, and we would rather say so than show you something unrelated.
Questions about Flutter projects
What buyers ask before choosing Flutter.
How much cheaper is Flutter than building two native apps?
Flutter or React Native?
Can the same code be our website too?
Can you take over an old Flutter app?
Tell us what the app has to do on the phone
Send the feature list and the devices your audience uses. We will come back with whether Flutter suits it and the questions that affect cost.
We reply within one business day (IST).