Who’s using Flutter?

As you may expect, Flutter users come from all kinds of backgrounds. When we asked about their experience in different mobile platforms (a multiple choice question), Android was the most popular (67%), followed by Web (45%) and iOS (30%). We saw a sizable growth in the proportion of Flutter users coming from a Web background, given that it was 33% in the survey in April. While the ratio of Android developers and iOS developers largely reflects the global user base imbalance of these two technologies, we are working on ways to attract more iOS developers to the Flutter community.

More Flutter apps coming in the wild?

We also found that 15% of the respondents have already published a Flutter app, and more excitingly, 52% are working on an app to be released within the next 6 months! We are looking forward to seeing these beautiful apps roll out to millions of mobile users.

Are users satisfied with Flutter?

Our users were generally satisfied with Flutter. 92% of the respondents said that they are very satisfied or somewhat satisfied with Flutter. They were also willing to recommend Flutter to others; more than half (56%) of the respondents gave 9 or 10 to the likeliness of recommending Flutter to others, on a scale of 0 to 10.

When it comes to fast development and beautiful UIs that Flutter strives to support, 79% found Flutter extremely helpful or very helpful in both reaching their maximum engineering velocity and implementing an ideal UI. This is the first time we asked this question in our user survey. We will continue to monitor and strengthen our core value proposition — “build beautiful native apps in record time” — in future surveys and other types of research.

How about Flutter’s documentation?

Documentation is a key aspect of great developer experience. We’ve seen users praise how well Flutter is documented, yet from a previous survey documentation is also the area that users wanted us to do more. So in this survey, we had a section of questions devoted to better understanding documentation needs and pain points from our users.

The results show that the quality of Flutter’s existing documentation is highly regarded by users (93% of respondents consider the quality good, very good, or excellent). However, there is clearly room for adding more sample code, making it easier to find samples, and improving the ability to learn how to use widgets from API references.

In addition, hundreds of users took the time to leave comments in this section of the survey. Thank you so much! We held a workshop to read through these comments and discuss what we can do to make Flutter better. In this workshop, we organized comments into high-level topics and sub-topics. From this exercise, it’s clear that having example snippets in each widget’s API doc is important. We’re making progress, and we welcome community contributions to our docs. Adding a missing snippet to a widget’s API doc is one of the simplest yet impactful contributions you can make to the Flutter ecosystem. If you’re interested in contributing, refer to the Flutter repo style guide and get started with pages listed in this bug.

The results also reinforced what we found earlier in our UX studies — having visual illustrations in documentation helps developers learn Flutter more effectively. Finally, we’ve received many comments requesting better guidance on state management. We’re actively working on more samples and articles on this very topic.

We took all this feedback to heart. We were also heartened by some compliments users wrote in the survey. For example:

“Flutter is amazing, it’s made my job as a programmer infinitely more enjoyable. Please keep up the great work!” “This framework is absolutely awesome!!! I have built very complicated UI in no time, the load time is fantastic! especially in comparison to nativescript, also the layout is extremely flexible and easy to use. I am so happy!!!” “I’m incredibly satisfied with flutter and the community. I’m looking forward to a desktop solution as well.”

And are there more Cupertino widgets?

This short answer is Yes! In this survey, we asked users who had experience using Cupertino widgets to tell us what we can do to improve the ability to build UIs in the iOS style. The top request was for more Cupertino widgets. We’re happy to report that we have made significant improvements over the past few months. For example, we recently added CupertinoApp, a convenience widget that wraps a number of widgets that are commonly required for an iOS-themed application. We’ll continue improving the Cupertino library based on community feedback.