Flutter in 2027: What Changes, What Stays, and Why There Is Still No 4.0

Our outlook on a possible Flutter 4.0 has become one of the most-read articles on this site. Its answer still holds in late 2026: there is no Flutter 4.0, and nothing on Google’s schedule points to one. However, the version number was never the useful question. The useful question is what Flutter in 2027 will demand from the teams that build on it.

So this outlook covers three things. First, what Flutter actually shipped in 2026. Second, the changes already in the pipeline. Third, the platform deadlines that will force upgrades whether you plan them or not.

Why there is still no Flutter 4.0

Flutter does not use semantic versioning. Instead, its official versioning document describes a modified calendar scheme. The minor number rises with time, while the major number moves only when the product team decides a milestone deserves it. That is why stable releases jump by three each quarter: 3.41 in February 2026, 3.44 in May, 3.47 in August, and 3.50 in November.

These major numbers track product milestones, not the volume of breaking changes. Flutter 3 arrived on May 11, 2022, to mark the move from mobile-first to multiplatform. By contrast, the biggest language break in years, Dart 3 with mandatory null safety, shipped inside Flutter 3.10 as a minor release.

Meanwhile, the 2026 roadmap commits to at least four stable and twelve beta releases. It doesn’t mention Flutter 4, a long-term-support channel, or a change to versioning. In other words, a 4.0 announcement is possible, but nothing published today supports expecting one.

The practical point lies elsewhere. Flutter’s breaking-changes page lists 49 migration guides across the seven stable releases from 3.29 to 3.47, roughly seven per release. Therefore, the version number tells you almost nothing about upgrade cost. The migration guides do.

What Flutter shipped in 2026

Flutter kept its quarterly rhythm all year. Each feature release then received seven to nine hotfix releases. At the time of writing, stable is 3.47.7 from October 8, and the 3.50 beta followed on October 14. Stable 3.50 is expected in November.

Dart moved more quietly. Primary constructors, which cut boilerplate in data classes, became stable in Dart 3.13 in August. Outside the framework, Google released Genkit Dart 1.0 on October 8. It gives Dart apps one API for AI features across Gemini, Claude, and OpenAI models.

The biggest change for Flutter in 2027: Material leaves the core

For most teams, the biggest structural change ahead isn’t a feature. It is where the widgets live. Since 3.44, the Material and Cupertino libraries inside the SDK have been frozen. Then, with 3.47, Google published them as separate packages, material_ui and cupertino_ui, at version 1.0. The 3.50 beta now marks the in-SDK libraries as deprecated and points developers to the packages.

There is no removal date. Moreover, Flutter no longer follows its old rule of removing deprecated APIs after a year. For example, describeEnum was deprecated in 2023 and is still present in 3.47.7. So nothing breaks overnight. Instead, apps that keep the old imports will slowly drift away from where the fixes land.

The upside is speed. These packages follow semantic versioning and can release weekly, and material_ui went from 1.0.0 to 1.7.0 in its first two months. The migration itself starts with one command, dart fix --apply --code=migrate_design_widgets. Run it on a branch, then review the result by hand.

iOS: the April 2027 cut-off

Apple has confirmed that from April 2027, uploads to App Store Connect must be built with the iOS 27 SDK and target iOS 15 or later. It has not yet published an exact date. Flutter is already prepared, because 3.47 raised its own minimum to iOS 15 for exactly this reason.

The version you run still matters. Flutter releases before 3.44.8 cannot build with the Xcode 27 toolchain at all. Furthermore, the 3.47 hotfixes kept fixing iOS 27 problems through September, including a white-screen hang when debugging with Xcode 27. Since Flutter hotfixes only its latest stable line, 3.47.5 or later is the realistic floor for iOS 27 work today.

Two migrations sit underneath the deadline. First, apps built with the iOS 27 SDK must adopt the UIScene lifecycle, or they fail at launch. Flutter migrates projects automatically, but only when the AppDelegate is unmodified. Apps with custom startup code therefore need a manual pass.

Second, CocoaPods is winding down. Its central repository will become permanently read-only on December 2, 2026. The maintainer says that date could slip later, but not earlier. Flutter already defaults to Swift Package Manager, and 92 of the top 100 iOS plugins had migrated by August. Any plugin that has not is now a risk on your dependency list.

Android and foldables: adaptive layouts stop being optional

Google Play has required new apps and updates to target Android 16 (API 36) since August 31, 2026. Next comes Android 17 (API 37). Google’s Android Developers Blog says Play will require it by August 2027, although that date is not yet in the Play policy itself.

The behavior change is the part to plan for. Apps targeting Android 17 lose control of orientation and aspect ratio on any screen at least 600dp wide. As a result, SystemChrome.setPreferredOrientations stops working on tablets and unfolded foldables. The Android 16 opt-out no longer applies, and Flutter’s own guidance is to make the app adaptive.

Flutter’s default target is still API 36, so apps on the default are not affected yet. That buys time, not an exemption. Meanwhile, Apple adds the same pressure from the other side with its foldable iPhone Duo. Apps built with the iOS 27 SDK resize to fill most of its inner display. An open Flutter issue shows a portrait-only app rotating when the device unfolds, and a Flutter engineer called this expected, comparing it to an iPad. For 2027, then, a phone-only layout is a liability on both platforms.

Our article on iOS 27 and Android 17 covers both platform changes in full.

Is Google still committed to Flutter?

This question drives most searches for Flutter 4.0. The answer depends on whether you read roadmaps or shipping software.

The shipping record is solid. Flutter’s showcase lists 13 Google products built with it, including NotebookLM, Google Pay, Google Earth and Google Classroom. Toyota ships Flutter in the in-vehicle software of the 2026 RAV4. Closer to our own markets, Grab has advertised Flutter roles for its merchant app in Jakarta this year—moreover, the release cadence held through all of 2026.

Google also reports 1.5 million monthly developers and 1.3 billion package downloads a month. Those are Google’s own figures, published without a method, so treat them as direction rather than measurement. Independent signals point the same way, though. The main Flutter repository has passed 180,000 GitHub stars, while Flock, the best-known community fork, has seen no code pushed since December 2025.

By contrast, the roadmap record is weaker. The 2026 roadmap calls itself “aspirational” and “a statement of intent and not a guarantee.” Dart macros, demonstrated at Google I/O 2024, were canceled in January 2025. Augmentations, promised in their place, have still not shipped. Developers seem to have priced this in: in Flutter’s own mid-2026 survey, 83% trusted Flutter, but only 62% trusted Google.

Our reading is straightforward. Plan on what has shipped, and treat the roadmap as a hint.

Where Flutter is still weak

An honest outlook needs the other side too. Four gaps matter for business apps.

• iOS design fidelity. Flutter’s Cupertino widgets still lack Apple’s Liquid Glass design, more than a year after iOS 26 shipped. The tracking issue is open at low priority. Unsurprisingly, Cupertino is the lowest-rated area in Flutter’s own survey, at 61% satisfaction.
• Web content and SEO. Flutter’s documentation says its web output does not suit search indexing or text-heavy pages. In fact, the Flutter team rebuilt Flutter.dev and dart.dev with a different framework, Jaspr. Use Flutter web for app-like tools behind a login, not for marketing pages.
• Embedded native views. Maps and web views inside a Flutter screen can stutter on Android during fast scrolling. The fix, Hybrid Composition++, is still opt-in and needs Android 14 or later.
• Desktop. Google handed desktop stewardship to Canonical in May 2026, and multi-window support remains experimental.

These gaps have real consequences. In October 2026, ResortPass announced it is rebuilding its iOS app natively in SwiftUI, replacing about 165,000 lines of Flutter. It cited faster access to new platform features, vendor SDKs without Flutter support, and hiring. Notably, its Android app stays on Flutter.

Should you start a new Flutter project in 2027?

For most of the apps we see, yes. Flutter remains a strong fit when:

• You need iOS and Android from one team and one codebase.
• Your app follows its own brand design rather than a strictly native look.
• It is an internal, field, or enterprise tool, where delivery speed outweighs platform polish.
• Web or desktop is a secondary, app-like target.

On the other hand, think twice when:

• Your product must match the newest iOS design on day one.
• Key vendors offer native SDKs only.
• Search traffic to your web pages drives the business.

Part 4 of this series compares Flutter, React Native, and Kotlin Multiplatform side by side.

How to prepare your Flutter app for 2027

1. Move to 3.47.5 or later now. Then schedule 3.50 within weeks of its stable release.
2. Check your AppDelegate. Custom startup code means a manual UIScene migration before you build with Xcode 27.
3. Audit your iOS plugins. Confirm Swift Package Manager support before CocoaPods goes read-only.
4. Run the Material migration on a branch. Review the diff now rather than waiting for a removal date.
5. Test at 600dp and wider. Include foldables, and remove orientation locks to see what users will see.
6. Budget one upgrade window per quarter. Flutter has no long-term-support channel, so an older release stops receiving fixes once its successor ships.

How Pegotec helps

We build and maintain Flutter apps, often paired with a Laravel back end. Our upgrade estimates start with the migration guides and the dependency list, because that is where the real work hides. As a result, clients know what their app needs before the April deadline, not after a failed upload.

If you want a 2027 readiness check on an existing Flutter app, talk to us.

Read next

• iOS 27 and Android 17: What Developers Need to Know — the platform changes behind the 2027 deadlines.
• Full-Stack Mobile Apps with Laravel and Flutter — the stack we pair with Flutter.
• iOS App Store vs Google Play 2026 — fees, review times, and release planning.

FAQ