---
Hey folks! Kevin, product manager on Flutter and Dart here.
The layoffs were decided AT LEAST a couple of layers above our team and affected a LOT of teams. (I think I can say that). Lots of good folks got bad news and lots of great projects lost people. Flutter and Dart were not affected any more or less that others. It was a tough day...tough week.
It was crazy to be seeing demos and new things working and discussions about new customers the same day we lost colleagues and friends.
We're sad, but still cranking hard on I/O and beyond.
We know ya'll care SO MUCH about the project and the team and the awesome ecosystem we've built together.
You're nervous. I get it. We get it.
You're betting on Flutter and Dart.
So am I. So is Google.
I'm just saying Kevin statement is meaningless. If you look at Google actions before, they do not slowly remove support from things and announce it. They silently layoff, go quiet then BAM, X is gone without warning and little time to deal.
> So am I. So is Google.
RIP Dart and Flutter.
There were some rumors that made people think of the worst, and as we speak about Google, a lot of people panicked that Google is dropping Flutter.
However, that was not the case.
They moved some roles to new locations, meaning (they claim) the team size change is net zero. https://x.com/MiSvTh/status/1785767966815985893
I get your frustration. Google just killed two of my favorite products this month (or more accurately, I found out about them this month), and then I heard about the Flutter downsizing rumors. I worked with Flutter for years now, and I decided that I can't let my professional fate in a company like that and started learning something new to switch to. Even if today it looks like they let Flutter live, it's better be prepared and pack up while I can leave on my own terms.
Already did 5 years ago.
https://sunrisetv.ch/de/vod/1/details/vod/crid:~~2F~~2Fog.li...
If you are going to create simple static homepage or interactive website, I don’t think Flutter is the right tool. Full fledged cross-platform applications is what Flutter is meant for.
Websites should still support accessability, I would even go as far to say it's a must. I just don't want people to mix up web-applications with websites. I've seen some people create a simple "websites" with Flutter which is totally pointless because it could just been created with html + css.
There is also a section in the Flutter docs that talks about accessability and how you can create accessable apps but I don't know how well it translates to Flutter web.
https://docs.flutter.dev/ui/accessibility-and-internationali...
I think all cross platform frameworks come with some kind of drawbacks and in most cases, learning about the underlying native platforms is unavoidable (like widgets, visionOS support etc).
So I wouldn’t worry too much or get into a FOMO decision block - I’d pick the one that feels most fun and fits your use case.
If you don't mind writing the UI native, sharing only business logic code, Kotlin is an option: https://kotlinlang.org/docs/multiplatform.html#kotlin-multip...
Kotlin also can do the UI if you use Compose: https://www.jetbrains.com/lp/compose-multiplatform/ ... however, iOS support is still in alpha, and Web is "experimental". If you're not willing to cope with that (expect to have to change your code as they develop the framework) then Flutter is the way as it's pretty stable already on all platforms.
If you already know Typescript and React, you may also consider React Native (but I can't attest to its performance on iOS or anywhere else): https://reactnative.dev/