Google's Flutter team shared results from its Q2 2026 developer survey, covering over 3,500 respondents. Overall satisfaction held at 93% while 'very satisfied' rose to 58%, and trust in Flutter climbed to 83%. AI coding agents like Claude Code (32%) and Antigravity (23%) now outpace GitHub Copilot, Cursor, and Codex in daily use. Cupertino widgets saw the steepest satisfaction decline (down 6 points to 61%), prompting the team to decouple Material and Cupertino widgets into separate pub.dev packages (material_ui and cupertino_ui) shipping in the August release. Android tooling upgrade pain remains the top complaint, addressed through recent Gradle/Kotlin/AGP compatibility work across Flutter 3.29 through 3.44. The team also announced a forthcoming formal four-tier Contributor Ladder to open up maintainer roles beyond Google.
Table of contents
Satisfaction is up, especially for new Flutter devs 🚀AI coding tools have moved from experiment to default ✨Where the experience still falls shortCupertino widgets: a new chapterTrust in Flutter, as our community model keeps evolvingWhere responsiveness still lagsThank you 💙What's next?Questions this post answers
What AI coding agents are Flutter developers using most, and how do they compare to GitHub Copilot and Cursor?
Claude Code leads AI coding agent usage among Flutter developers at 32%, followed by Antigravity at 23%, both ahead of GitHub Copilot at 19%, Cursor at 18%, and Codex at 17%. Traditional IDEs still dominate overall, with VS Code at 66% and Android Studio at 40%. Satisfaction is high across most tools, with VS Code at 88% and Claude Code at 86%, while Zed trails at just 38% satisfaction despite low usage. Developers choosing an AI coding agent for Flutter work can track adoption and satisfaction trends on daily.dev.
Why are Cupertino widgets being split into a separate package from Flutter core?
Cupertino widgets are being decoupled from Flutter's core framework and published as a standalone cupertino_ui package on pub.dev, alongside a new material_ui package, starting in the August release. This lets native design fidelity iterate on its own schedule instead of being gated behind core framework release cycles, following a steep 6-point satisfaction drop to 61% for Cupertino widgets, the lowest-rated area in the survey. Teams building iOS-style Flutter apps can follow how cupertino_ui evolves independently on daily.dev.
What changed in Flutter's Android build tooling to reduce Gradle and AGP version conflicts?
Flutter 3.29 removed legacy script-based Gradle plugin applications to reduce breakage with new AGP versions, Flutter 3.32 rewrote the Gradle plugin from Groovy to Kotlin for stability, Flutter 3.38 published an official version matrix across Java, Kotlin, AGP, and Gradle, Flutter 3.41 added AGP 9 support, and Flutter 3.44 migrated to built-in Kotlin. Developers untangling Android build upgrades can track these Flutter release changes on daily.dev.