Flutter Q2 2026 Survey: What 3,500 Developers Told Google

Every quarter, the Flutter team runs a survey through the IDE plugins (VS Code, IntelliJ, Android Studio), X, and the Flutter website. The Q2 2026 edition ran from June 8 to June 22 and collected more than 3,500 complete responses. The results, published on the Flutter blog, are the strongest in the survey’s history — with a few sharp warning signs that the team is now moving to address.

The Headline Numbers

• Overall satisfaction: 93% (top-2 box), steady versus Q4 2025 — but the composition improved markedly. “Very satisfied” rose from 52% to 58%, while “somewhat satisfied” dropped from 40% to 35%. Developers are not just satisfied; more of them are emphatic about it.
• Trust in Flutter rose from 77% to 83%. Trust in Google, by contrast, sat at only 62%. Flutter as a product now leads its parent company by more than 20 points across every company-size segment.
• For the first time in the survey’s history, every subgroup — every experience level, company size, and platform combination — reported 90%+ overall satisfaction.

Satisfaction by Area

Area	Satisfaction
Dart language	92%
Android app development	91%
Core framework	90%
Windows	74%
Linux	73%
Web	72%
Cupertino widgets	61%

The Dart language remains the highest-rated component of the ecosystem — a consistent result across recent surveys. Web, Linux, and Windows all improved versus Q4 2025, which aligns with the 2026 roadmap’s investments in Wasm-by-default web and desktop-first-class support.

Two findings stand out less happily:

Cupertino’s steep decline. At 61%, Cupertino widgets are the lowest-rated area, down 6 points — the steepest decline anywhere in the survey. Developers feel iOS-style native design has lagged behind, a perception reinforced by Apple’s own design evolution (Liquid Glass) outpacing the widget set.

The novice gap. Novice developers hit 90% overall satisfaction (up 5 points), but only 82% on the core framework versus 93% for experts — an 11-point gap that says the framework’s learning curve remains steep for newcomers.

Editors and AI Tools

Respondents could select multiple tools:

• VS Code: 66% usage, 88% satisfaction — still the center of gravity.
• Android Studio: 40% usage.
• Claude Code: 32% usage, 86% satisfaction — now the most-used AI coding agent for Flutter developers.
• Antigravity: 23% — Google’s agentic IDE, which received a dedicated Flutter plugin this year, already commands a quarter of respondents.
• GitHub Copilot: 19%, Cursor: 18%, Codex: 17% (85% satisfaction).
• Zed: just 38% satisfaction on only 5% usage — the clear outlier, far below every other editor.

The story here is the passing of a milestone: AI coding agents (Claude Code, Antigravity) have overtaken the first-generation AI assistants (Copilot, Cursor) among Flutter developers. This matches the roadmap’s own positioning of Dart and Flutter for an “AI-first” developer persona, with tooling like the Dart MCP server, Agent Skills, and agentic hot reload built for exactly this workflow.

What Is Driving Dissatisfaction

Four themes accounted for the dissatisfaction feedback:

1. Platform/ecosystem maturity (44%) — dominated by Android upgrade pain: Gradle, Kotlin, AGP, and JVM version conflicts that surface every time a project or plugin needs updating.
2. Tooling/IDE experience (33%) — desire for deeper Android Studio integration and better AI tooling.
3. Bugs and stability (24%) — debug tooling issues, notably persistent breakpoints and a confusing performance timeline.
4. UI/UX aesthetics (14%) — tied directly to Cupertino’s decline.

How the Flutter Team Is Responding

The blog post paired each concern with concrete actions, several already shipped:

Android upgrades. The Kotlin-rewritten Gradle plugin landed in 3.32, an official version matrix arrived in 3.38, and AGP 9 support shipped with 3.41. Release blogs now include compatibility matrices, and smart build fallbacks are being explored so version mismatches degrade gracefully instead of failing the build.

iOS/macOS. Swift Package Manager became the default in Flutter 3.44, replacing CocoaPods — and 92 of the top 100 iOS plugins have already migrated.

Cupertino and Material. The August 3.47 release decoupled the design systems into standalone material_ui and cupertino_ui pub.dev packages, precisely so Cupertino can iterate independently — enabling both Material 3 Expressive and Apple’s Liquid Glass to ship on their own schedules rather than waiting for framework releases.

AI tooling. The Dart MCP server, Agent Skills, agentic hot reload, and the Antigravity plugin are all live; the team is exploring how to surface AI guidance to novices earlier in the onboarding path.

Governance: The Bigger Story

One survey statement — “the Flutter team is responsive to my needs” — drew only 71% agreement, more than 10 points below every other statement. The response is a structural overhaul of how the project takes feedback and distributes maintainership:

• Consultancy Program expansion, a larger Google Developer Expert network, and new Customer Advisory Board and Partners Advisory Board as formal feedback channels.
• A proposed four-tier Contributor Ladder — Contributor → Reviewer → Committer → Maintainer — with public, data-driven promotion criteria.

The Contributor Ladder matters beyond optics: more than 70% of open PRs now come from non-Google contributors, and for new features, survey respondents preferred “battle-tested by the community” (41%) over “built by Google engineers” (26%). Framework performance and stability (26%) ranked as the top trust driver, ahead of community size (20%) and documentation (19%) — but the governance signal is clear that the ecosystem wants a maintainer base that reflects who is actually writing the code.

What to Watch

Three threads from this survey are worth tracking through the rest of 2026:

1. Whether the standalone cupertino_ui package reverses the 61% score. It is the clearest test of whether decoupled design systems can move faster than the monolithic framework did.
2. Whether the Contributor Ladder ships and begins shifting commit and review authority toward community maintainers.
3. Whether Antigravity and Claude Code usage keeps climbing — and whether Zed’s 38% satisfaction either recovers or cements VS Code’s position as the default Flutter editor.

The overall picture is of an ecosystem at peak measured contentment, with a trust deficit aimed not at the framework but at the institutions around it — and a team responding by distributing power rather than defending it.

References

• Flutter Q2 2026 survey — flutter.dev
• Flutter & Dart 2026 roadmap
• What’s new in Flutter 3.47
• What’s new in Flutter 3.44