Now that the dust has settled on the news of layoffs at Google, let’s take a quick look at what this means for Flutter.

Unnecessary drama

The news of layoffs in the Flutter team had no detail — was 1% of the team effected or 50%? It was not clear.

Without concrete information, the rumour mill went into overdrive (perhaps not without good reason…more on that later).

Eventually, Michael Thompson from Google clarified the situation. Basically the changes to Flutter effected some of the DevOps roles, but otherwise the team size stays the same.

X Post from Michael Thomsen

TL;DR — the news headlines created a lot of unnecessary drama but the reality is actually that nothing substantive is changing.

Google creates FUD

What this week has showed (again), is that Google has created a lot of mistrust in it’s commitment to products and projects.

Google is really damaging it’s brand with all the high profile projects being killed which is exacerbated by the volume of small ones — see https://killedbygoogle.com/.

Whilst the Flutter technology is strong, the community vibrant and the real world backing plentiful, Google is making is much harder for companies to invest in building Flutter-based software.

Too big to fail?

Created with Copilot

Despite Google’s efforts to scare the Flutter community, our view is that Flutter has crossed a threshold that makes it too big to fail.

Let’s just look at who is betting on Flutter:

Toyota is using Flutter to build its next gen Infotainment Systems that will be in thousands of cars across the globe. Read more.
Ubuntu 23.04 shipped with a new installer tool written in Flutter. Canonical (the company behind Ubuntu) has indicated that it would use Flutter as the technology for future desktop app development. Read more.
Google Earth for mobile and web was rewritten in Flutter, another signal that Google’s engineers are betting on Flutter. Read more.
Google Pay on iOS and Android was implemented using Flutter. Another sign of Google’s commitment. Read more.
Google Classroom rebuilt it’s mobile apps using Flutter having been inspired by what the Google Pay team were able to achieve. Read more.
Alibaba built Xianyu (a 50+ million user marketplace) using Flutter
eBay built the eBay Motors mobile app using Flutter. Read more.

The investments in Flutter from inside Google and from the community are a good indicator that Flutter has survived it’s infancy.

Slowing adoption

Whilst we believe that Flutter is here to stay, there are questions about the rate of adoption.

On the Flutter showcase page, you will see the projects from the biggest brands are from 2021. Canonical’s bold claims that they are “making Flutter the default choice for future Canonical mobile and desktop apps” have not yet translated into reality.

The Flutter leadership team (e.g. Eric Seidel, Tim Sneath) that achieved initial success have moved onto other companies or projects.

Google is great at getting projects into the world and creating initial adoption. However, it has proven itself less able to stick it out during the long hard road to widespread adoption.

Google needs to double-down on Flutter through this adoption phase — as it did with Angular, Android, Golang and many other great contributions.

Will it do so? That’s the question looms large in light of the latest round of layoffs.

If the Flutter team is allowed to continue on it’s current trajectory, there are signs that they will continue to make good progress. For example see this Reddit post: Headspace (65 million users) is migrating to Flutter.

Our prediction

Created with Copilot

Our general expectation is for the mobile development landscape to shift towards a more efficient model for building across multiple devices. Flutter will be an importat part of that story on mobile.

However, we see great opportunity for Flutter to also flourish outside the mobile world.

Flutter could be key to widespread adoption of WebAssembly, a way to run compiled applications in the browser — see Figma’s WebAssembly story. The Flutter team already have Wasm support in Beta.

At Snapp, we are also betting on Flutter as a modern replacement to Qt for UI development for embedded software. The Snapp Embedded project from our sister company, Snapp-X is building the tooling to make this possible and we are already working with one of the world’s largest manufacturers of white goods (freezers, ovens, washing machines) to build device UIs using Flutter.

For more widespread adoption, Flutter will need to show how it is truly cross platform with massive code reuse across mobile and web. This is one of the biggest advantages over ReactNative — the incumbent for non-native mobile development.