Flutter is Google’s open-source toolkit for building apps for iPhone, Android, the web and desktop using a shared set of code. Developers write in a language called Dart and use Flutter to put text, buttons, forms, animations and other interactive elements on screen.
Imagine a coach wants an app that shows an athlete the movement they made five seconds ago. The phone sits on a tripod. The athlete finishes a jump, turns around and watches the replay while they can still remember how the landing felt. If it is worth keeping, the coach presses “Save last clip”.
Flutter can draw that button, make it large enough to use at arm’s length and show whether a clip is ready. The phone’s camera has a different job. It must keep capturing video while the athlete watches an earlier moment. Understanding how those two jobs fit together explains both the appeal of Flutter and where a project can get difficult.
What do Flutter, Dart and the Flutter SDK actually mean?
Dart is the programming language. It lets a developer express instructions such as “when five seconds of footage are ready, enable the save button”. You can write Dart code that calculates a duration or organises a list of clips without putting anything on screen.
Flutter is the framework. It supplies reusable pieces for building the interface and rules for how those pieces work together. A developer can tell Flutter what the screen should look like while the camera is starting, then what it should look like when a replay is ready.
The Flutter SDK is the set of tools the developer installs. SDK stands for software development kit. It includes the framework and tools to run, test and build the app. The coach installs the finished app. Only the development team needs the kit used to make it.
How does a Flutter widget work?
A widget describes part of a Flutter interface. A line of text can be a widget. So can a button, a row that positions two buttons side by side, or an entire screen made from smaller widgets. In Flutter, the term applies to the pieces inside an app as well as the layouts that hold them.
Consider the first few seconds after the coach starts the camera. A button labelled “Save last clip” would be misleading while the phone is still gathering footage. The app needs to remember one fact: whether a clip is ready. Developers call a fact like this state. Here is how a small piece of a Flutter screen could use it.
FilledButton(
onPressed: clipReady ? saveLastClip : null,
child: Text(clipReady ? 'Save last clip' : 'Waiting for footage'),
)
Read the first line inside the button as a question. Is the clip ready? If it is, pressing the button runs the app’s saveLastClip function. Otherwise, the button receives no action and stays disabled. The next line gives the athlete a visible explanation. When the app updates the state and rebuilds this widget, the label and the action change together.
During development, Flutter’s hot reload can apply many interface edits while keeping the current screen open. A developer trying a larger button can often inspect the change without repeating the whole setup. To judge whether the button is readable from the landing mat, though, someone still needs to put the phone on the tripod and stand where the athlete stands.
What does “one codebase” let you share?
A codebase is the set of source files a team maintains. In the replay example, the iPhone and Android versions could share the delay selector, the clip list, the wording on the save button and the rule for when saving becomes available. If athletes later ask for a ten-second delay, the team can change the shared control in one place.
The two phones still have different operating systems. Each handles camera permissions, interruptions and access to saved media in its own way. A plugin is a reusable package that can connect Dart code to capabilities like the camera. Before adopting one, check the exact operation your product needs. A plugin that records a video may still lack support for playing an earlier part of that video while recording continues.
Flutter produces a build for each target. An iPhone app and an Android app have their own release files, store submissions and device tests. Sharing the clip list saves duplicate work. Testing what happens when a phone call interrupts recording is still worthwhile on both platforms.
What kinds of apps can you build with Flutter?
- Booking and ordering apps. A restaurant customer can choose a time, enter the party size and review a reservation on either phone. Flutter can share that booking flow. A backend must check the live table inventory before the app promises a seat.
- Field tools that work through a connection loss. A technician can record an inspection in a basement and upload it upstairs. Flutter can present the form and show which reports are waiting. The team also needs local storage and a sync rule so that retrying an upload does not create a second inspection.
- Interactive web and desktop tools. A dispatcher might use a browser dashboard to assign jobs while a technician uses a mobile app to complete them. They can share job data and status rules. The dispatcher benefits from a wide layout and keyboard shortcuts, while the technician needs controls that are easy to tap on site.
- Puzzle and board games. A logic puzzle can share its board, move rules, hints and progress across platforms. A good first test is whether the densest board remains readable and responds accurately on the smallest phone you intend to support.
- AI-powered applications. Flutter can display transcripts, accept a correction or let someone search their notes. A model running on the device or a service running on a server performs the AI task. That choice determines whether the feature can keep working offline.
Flutter supports deployment to Android, iOS, web browsers, Windows, macOS and Linux. It can also be used in embedded products such as dedicated displays, where the hardware and the software that runs Flutter on it need to be evaluated together. For an existing customer base, check the operating systems customers actually use against Flutter’s supported deployment platforms.
Which real apps show what Flutter can do?
Google Classroom illustrates a mobile migration. Its team already had working apps and wanted to reduce the effort of supporting multiple platforms. Before choosing Flutter, it assessed factors including accessibility, memory use, app size and whether scrolling felt smooth. For a team replacing an existing app, that is a useful comparison: test the Flutter version against the experience customers already have. The team describes its evaluation in the Google Classroom case study.
Foresight illustrates a different use on desktop. Google AI Edge’s macOS meeting app can turn shorthand notes into structured notes and produce transcripts using models that run on the Mac. Flutter powers the interface, while native components handle work such as audio capture and model execution. For someone choosing a meeting tool, the meaningful feature is that it can process the meeting locally. The Foresight case study explains how the team connected those pieces.
Where is Flutter a weaker fit?
A public website built mainly for reading. Suppose a climbing gym wants its opening hours, prices and coaching articles to appear in search. Ordinary HTML suits those pages and lets visitors follow direct links, select text and read with familiar browser behaviour. An interactive route planner or members’ training log is a more plausible use for Flutter web. A business can use both approaches within the same product. Flutter’s web guidance makes this distinction explicitly.
An app whose value depends on one demanding device feature. Continuous recording, low-latency audio and a specialist hardware accessory all deserve an early test on the target device. If the manufacturer supplies a native library, find out whether Flutter can call the functions you need. When a product is intended for only one platform and much of its code would live in that native library, a native implementation is worth comparing before committing to Flutter.
An app that already works well. An existing iPhone or Android product can adopt Flutter for an individual feature. A self-contained booking flow is easier to evaluate than a complete rewrite. The team can measure startup time, accessibility and maintenance effort before deciding whether a second feature should follow.
What is the latest stable Flutter release?
As of , the latest stable release is Flutter 3.50.1 with Dart 3.14.0. Flutter 3.50 introduced the feature changes on 11 November. Version 3.50.1 is a maintenance update. For example, it fixes a problem that could leave certain assets out of an Android release build. The Flutter SDK archive lists the current stable version and its bundled Dart release.
One change in 3.50 matters if your idea depends on hardware. Flutter added stable tools that let Dart call Objective-C APIs on Apple platforms and Java or Kotlin APIs on Android more directly. If a camera manufacturer already supplies an Android library with a replay function, a team has another route to use that library from Flutter. It would still need to establish what the iPhone library supports. The Flutter 3.50 release announcement explains the integration options.
How would you decide whether to use Flutter for an MVP?
For my Android sports app Instant Replay, the first question was whether a real phone could keep capturing footage and show a delayed replay without unacceptable heat or battery drain. I started with a small proof of concept on a phone. The tripod also changed the interface requirements: a control that looks large in your hand can be hard to identify from several metres away.
I would use the same test when evaluating Flutter for a similar product. Pick the action someone would install the app for. Run it on the devices they own, for as long as they would actually use it. Check what happens when a permission is declined, storage runs low or the app is interrupted. A working ten-minute training session tells you more about the choice of framework than ten polished settings screens.
If you are planning an iOS and Android MVP, start with the one action your first customer needs to complete. I can help you decide which parts to build once in Flutter, what to test on each phone and where a backend is needed. Explore my mobile development and backend expertise.