Dart and Flutter build
The screens are composed from Flutter widgets and the logic written in Dart, in a project that follows the structure Flutter’s own tooling expects. You receive: the source code in your repository, with build notes.
Flutter app development
We build your app in Flutter when one codebase costs you less, and tell you plainly when two native apps would do better.
Get your Flutter app scoped in writingWhat Flutter development is
Flutter app development is building an app in Google’s Flutter toolkit and the Dart language, so iPhone and Android run the same code. Flutter draws its own interface instead of borrowing each platform’s, which is where both the savings and the trade-offs come from.
The screens, the logic and the data handling live in one Dart project, so a change to the booking flow is made once and lands on both phones.
Flutter paints every pixel itself through an engine called Impeller, so a button is drawn the same way on iPhone and Android by design. Older Android phones use a different drawing path, which is why we test them.
For a card reader, a Bluetooth lock or a health sensor, a small piece of Swift or Kotlin sits behind the Dart code. The rest of the app stays shared.
The decision
The better one depends on the app, and the written scope names which we recommend and why.
| NativeSwift and Kotlin, separately | FlutterOne codebase, two stores | |
|---|---|---|
| Code to build and maintain | A Swift project and a Kotlin project, each with its own releases | One Dart project for the shared screens, plus small native pieces where needed |
| How the screens look | Each phone’s own controls, which update with the operating system | Identical on both phones, drawn by Flutter’s engine, with Material and Cupertino styles available |
| New phone features | Available the day Apple or Google ships them | Reached through packages or a platform channel, which can lag a new OS release |
| Hiring a later team | An iOS group and an Android group | Flutter and Dart developers, one group for both phones |
| A good fit when | The app leans on the camera, AR, heavy graphics or the newest platform features | Most screens are forms, lists, bookings and checkout, and the budget is one team’s |
We list the app’s screens and device features, mark which need native code, and price both routes. If the native share is large, the scope recommends native and says what the saving would have been.
The documentation
Each comes from the Flutter or pub.dev documentation, named under it.
Flutter’s docs say there is no switching back to Skia on iOS. Impeller precompiles a smaller set of shaders when the engine is built, so they are not compiled at runtime.
On older versions of Android, or phones without Vulkan, Flutter falls back to its older OpenGL renderer. That makes older phones a real test target, because the drawing path differs from newer ones.
Dart and the phone talk by passing messages: Kotlin or Java on Android, Swift or Objective-C on iOS. The docs also describe Pigeon, a package that generates type-safe code on both sides.
The Web FAQ names blog articles as a poor fit and says Flutter web output does not align with what search engines need to index. It suggests keeping marketing and help content in search-friendly HTML and the app itself in Flutter.
Those are the supported minimums, and anything earlier is unsupported. Your app can set a higher floor, and where it sets that decides how many older phones the build has to be tested on.
Pub points cover file conventions, documentation, platform support, static analysis, up-to-date dependencies and modern toolchain support. pub.dev calls the download count an imperfect metric, so we read the score and the release history together.
The scope
From the Dart code to the web question, each part names what you receive.
The screens are composed from Flutter widgets and the logic written in Dart, in a project that follows the structure Flutter’s own tooling expects. You receive: the source code in your repository, with build notes.
Figma screens turned into Flutter themes, with Material or Cupertino styling chosen per screen, then compared on an iPhone and an Android phone. You receive: the theme files and a side-by-side screenshot set.
Swift and Kotlin code behind a typed channel for the features Flutter has no package for, such as a studio’s door reader. You receive: the channel definitions and the native source.
Packages are listed with their pub points, release history, open issues and license. You receive: the package list with a verdict beside each.
Builds run on the iPhone and Android versions your users carry, including phones on the older Android drawing path, as set in the written scope. You receive the issue list and a log of the devices the builds ran on.
A short assessment of whether a browser or desktop version earns its cost, using what Flutter’s docs say the web target is good for. You receive: a one-page recommendation, and a build only if you approve it.
How it runs
You approve each stage before the next, and the store accounts are in your name from the first day.
First version scope
| Feature | First version | Note |
|---|---|---|
| Class schedule and booking | Yes | Shared Dart code on both phones |
| Memberships and card checkout | Yes | Apple Pay and Google Pay |
| Studio door check-in | Yes | Native code for the door reader |
| Waitlist alerts | Yes | Push notifications |
| Front-desk web view | Later | Revisit after launch |
| Apple Watch app | Later | Not worth a native build yet |
Our stack
What the Flutter app is designed, written, tested and shipped with. Open a card to see the job that tool does in the Flutter build.
Flutter is Google’s toolkit for building apps for phones, the web and desktop from one codebase.
The app’s screens and logic are written in Flutter and Dart, so any Flutter developer you hire later can read them.
Questions
Keep exploring
Business software built around how you work, in your own repository.
Swift and SwiftUI iPhone apps, built in your own Apple Developer account.
Kotlin and Jetpack Compose apps, published from your own Google Play account.
Engineers on your product, working in your GitHub, Jira and Slack.
A remote team building in your repository, with the code in your name.
A first version at a fixed price, with a list of what to cut.
Portals, dashboards and SaaS-style tools that run in the browser.
Software for larger organizations, built around the systems already in place.
One TypeScript codebase for iPhone and Android, in your own store and Expo accounts.
Start here
Tell us which screens the app has to run on. We’ll send back the first version’s features, whether Flutter or native fits better, and a fixed price for the first milestone.