Flutter statistics show a cross-platform toolkit with a large public development footprint and broad deployment coverage. The Flutter GitHub repository reports 177,000 stars, 30,400 forks, more than 5,000 open issues, and 482 pull requests. Its release notes list 25 stable releases, spanning versions 3.44.0 through 1.12.13. Together, these figures describe an active project, while the platform data shows where its applications are supported and where they are not.
Contents
- Repository and release snapshot
- Developer survey context
- Learning, tools, and working patterns
- AI adoption and developer expectations
- Mobile and desktop support
- Linux and browser support
Repository and release snapshot
The Flutter GitHub repository provides the clearest public indicators of project reach. It shows 177k stars, a measure of how many GitHub users have marked the repository for interest. The same page shows 30.4k forks, indicating that tens of thousands of repository copies have been created for independent work, experimentation, or contribution workflows.
The repository also lists 5k+ open issues. That number should be read as the size of the visible issue queue at the measurement point, not as a count of confirmed defects. Issues can include questions, feature requests, documentation work, investigations, and bugs. The page reports 482 pull requests, another snapshot of proposed changes in the repository’s contribution process.
Flutter’s GitHub page lists 18 topic tags. These tags provide a compact description of the repository’s subject areas and ecosystem positioning, but they are not a market-share measure. The useful takeaway is that the project has a substantial, discoverable public presence across code, issues, forks, and metadata.
The Flutter release notes page lists 25 stable releases from 3.44.0 through 1.12.13. This is a count of stable entries shown on that page, not a claim about every release channel or every patch version ever published. It does show that Flutter’s documented history includes a sequence of stable releases across a broad version range.
| Measure | Reported figure | Source label |
|---|---|---|
| GitHub stars | 177,000 | Flutter GitHub repo |
| GitHub forks | 30,400 | Flutter GitHub repo |
| Open issues | 5,000+ | Flutter GitHub repo |
| Pull requests | 482 | Flutter GitHub repo |
| Topic tags | 18 | Flutter GitHub repo |
| Stable releases listed | 25 | Flutter release notes |
These figures are best used together. Stars and forks indicate attention and reuse, the issue and pull-request counts show visible repository activity, and the release-note count describes the stable release list. None of them alone measures application quality, adoption in production, or popularity among end users.
Developer survey context
The Stack Overflow 2024 Developer Survey received responses from 65,437 coders in May 2024, representing 185 countries. The survey is broader than Flutter, so these figures provide context about the developer population rather than Flutter-specific usage. They help explain the environment in which a cross-platform framework is learned, evaluated, and maintained.
Several background figures describe respondents’ education and work status. Sixty-six percent reported having a BA/BS or MA/MS degree, while 49% said they learned to code at school. Eighty-four percent said they were working, either part-time, freelancing, or full-time. Among professional developers, 25% reported one to four years of work experience.
The survey also reports a strong reliance on online information. Eighty-two percent of developers said online resources were their top choice for learning to code, and 90% said API and SDK documents were their preferred documentation source. Ninety-three percent visited Stack Overflow at least multiple times per month, if not multiple times per day. Sixty-one percent spent more than 30 minutes a day searching for answers or solutions.
Account and salary participation add useful scale markers. The survey says 76.3% of respondents had a Stack Overflow account, while 48,019 respondents shared salary information. These are participation figures within the survey and should not be treated as estimates of all developers worldwide.
The survey’s language data also places Flutter in a wider development landscape: 62.3% of respondents said they had used JavaScript in the past year. That result does not measure Flutter usage, but it illustrates the prominence of a web-oriented language among the surveyed population.
Learning, tools, and working patterns
The survey’s tooling figures show how different groups approach development. PostgreSQL was used by 49% of developers in 2024. In the survey’s comparison data, PostgreSQL was used by 33% of developers when it debuted in 2018, while MySQL was used by 59% in that 2018 comparison year. These are survey percentages from different measurement points, so they should be read as reported snapshots rather than a controlled trend calculation.
Docker was used by 59% of professional developers. Among developers learning to code, 45% used npm. The categories are not interchangeable: one figure is specifically about professional developers, while the other describes people learning to code. They nevertheless show the range of infrastructure and package-management tools present in the survey’s development context.
Respondents also reported changing work arrangements. Forty-two percent worked in a hybrid environment, and 20% worked in person in 2024. The in-person figure was 15% in 2022 and 16% in 2023. These percentages indicate reported workplace patterns for the survey years; they do not establish why the figures changed or predict future arrangements.
Technology endorsement was associated with access in one survey result: 75% of developers were more likely to endorse a technology if it offered API access. For teams assessing Flutter in a media or streaming product, this points to the importance of integration surfaces, although the result is about developer preference generally rather than Flutter specifically.
AI adoption and developer expectations
The Stack Overflow 2024 Developer Survey records a sharp rise in AI-tool activity. Seventy-six percent of respondents were using or planning to use AI tools in their development process in 2024, compared with 70% the year before. Sixty-two percent were currently using AI tools in 2024, compared with 44% the year before.
The survey also records where developers expected AI tools to become more integrated. Eighty-one percent expected greater integration into documenting code the following year, 80% expected greater integration into testing code, and 76% expected greater integration into writing code. These are expectations, not measured future outcomes.
The results distinguish product admiration from future intent. Rust earned an 83% most-admired score in 2024. Among developers who used Svelte, 73% wanted to keep working with it. Among ChatGPT users, 75% said they wanted to keep using it, and a separate result says 74% wanted to use it the following year. Forty-one percent of ChatGPT users wanted to use GitHub Copilot the following year. Replit Ghostwrite or Tabnine received a 36% admired score, the lowest in that comparison.
Ethics and employment concerns were also quantified. Seventy percent of professional developers did not perceive AI as a threat to their job. At the same time, 79% said misinformation and disinformation in AI results was a top ethical concern, and 65% identified source attribution as a top ethical concern. These figures describe attitudes among survey respondents, not an assessment of the accuracy or safety of any specific Flutter-related output.
Mobile and desktop support
Flutter’s supported deployment platforms page describes mobile and desktop boundaries in concrete terms. Android support includes x64, Arm32, and Arm64 hardware architectures. Android is supported from API 24 to API 36 and CI-tested from API 24 to API 36. Android API 23 and earlier are listed as unsupported.
For iOS, Flutter supports Arm64. The supported version range is iOS 13 through iOS 26, with CI testing on iOS 18. iOS 12 and earlier are listed as unsupported. The support range and the CI-tested version are different pieces of information: support describes the stated compatibility boundary, while CI testing identifies the version named for automated testing on the page.
| Platform | Supported architecture or runtime | Supported range | Unsupported boundary |
|---|---|---|---|
| Android | x64, Arm32, Arm64 | API 24–36 | API 23 and earlier |
| iOS | Arm64 | iOS 13–26 | iOS 12 and earlier |
| Windows | x64, Arm64 | Windows 10 and 11 | Windows 8 and earlier |
| macOS | x64, Arm64 | Catalina 10.15–Tahoe 26 | Mojave 10.14 and earlier |
Windows support covers x64 and Arm64. The supported operating systems are Windows 10 and Windows 11, and the page names Windows 10 as the CI-tested version. Windows 8 and earlier are listed as unsupported.
macOS support covers x64 and Arm64, from Catalina 10.15 through Tahoe 26. The CI-tested version is Sequoia 15, while Mojave 10.14 and earlier are listed as unsupported. For a desktop media application, these boundaries matter when deciding which operating-system versions to include in testing and release support.
Linux and browser support
Flutter’s Linux support data names Debian and Ubuntu separately. Debian support covers x64 and Arm64 from version 10 through version 13, with CI testing on Debian 12. Debian 9 and earlier are listed as unsupported.
Ubuntu support also covers x64 and Arm64. The supported range runs from Ubuntu 20.04 LTS through Ubuntu 24.04 LTS, with CI testing on Ubuntu 22.04 LTS. The page lists Ubuntu 25.10 and earlier non-LTS releases as unsupported. The distinction between long-term-support releases and non-LTS releases is important when defining a Linux deployment matrix.
Browser support includes Chrome, Firefox, Safari, and Edge. Flutter supports Chrome with JavaScript and WebAssembly. Chrome support covers the latest two versions, and the page names version 145 as CI-tested; Chrome 95 and earlier are unsupported.
Firefox support uses JavaScript. The latest two versions are supported, version 148 is CI-tested, and Firefox 98 and earlier are unsupported. Safari support uses JavaScript, covers version 15.6 and newer, and is CI-tested on version 18.6. Safari 15.5 and earlier are unsupported.
Edge support includes JavaScript and WebAssembly. The latest two Edge versions are supported, version 145 is CI-tested, and Edge 95 and earlier are unsupported. Because browser support is expressed partly as a moving latest-two-versions policy, teams should check the current supported-platform page when setting a release matrix; the figures here describe the stated support information supplied for this article.