> near-native mobile apps (the difference is almost negligible)
Not as of the advent of Liquid Glass on iOS (and, to a lesser extent, Material Expressive on Android). Flutter isn't going to be implementing these new interface conventions[1], and so the UI for these apps are stuck on the last generation and are already starting to feel outdated.
Flutter's grim outlook has resulted in a surge of interest in Skip, and it was one of the drivers for us to open up the platform and catch the wave. If you love Dart, or if your apps don't need to look native (e.g., games or very bespoke interfaces), then Flutter might continue to be acceptable. But everyone else is starting to look elsewhere, especially in cases where their business depends on their apps feeling premium and native.
To be fair reading those updates it sounds a lot more positive than this comment makes it seem. I.e. "they're pausing design updates while they figure out the best way to do it" rather than "they're not going to bother":
> This strategic pause on design updates gives us the space to ensure the long-term health and maintainability of Flutter's design libraries. We are committed to being transparent with our contributor community as we explore these options and will have more to share on our findings and future direction in the coming weeks.
and
> The material and cupertino libraries are being decoupled into standalone packages to accelerate feature development. All new work for iOS26 updates in Cupertino will happen in the new packages once established in flutter/packages.
Compared to that, my (OxygenOS version of) Android UI is pretty good, concise, flexible and customisable if I want to. I hate the ambiguity of gestures, so I keep the buttons for navigation. I don't want everything splattered on the home screen, so I use a different launcher than the default. The menus are all logical.
Flutter can't even get animations to look and feel right for iOS 18 and below (read through this thread and every other HN/Reddit thread that mentions Flutter vs. native components). Do you really think they'll ever get Liquid Glass looking and feeling convincing, let alone performing acceptably?
Read over the 100+ comments in the GH issue I posted. You see actual Flutter contributors — not people who merely vibe-coded a Potemkin L.G. demo and declared victory — saying that it is effectively impossible.
[1] https://medium.com/@0s.and.1s/flutter-part-iv-skia-vs-impell...
That's also maybe why it's so popular in India.
The cost of making an excellent flutter app is about the same you'd pay making fully native apps. Except that you're always paying for Skia's costs with Flutter.
This recommends 32GB to run _everything_, so xcode, gradle, emulators, simulators, etc. Not fully surprising.
On an unrelated note, in 2024 Google did layoffs on the Flutter team.
Also, the layoffs were for infrastructure engineers who were working on Flutter builds not actual core Flutter devs. And the layoff was just an offshoring, they moved the same jobs from the US to Europe.
The question isn't if Flutter is dead. It's (1) will Google continue to invest resources to maintain it (and note they could easily make their commitment firm, and have chosen not to do so for obvious reasons: they value the optionality to stop support); and (2) if Google were to reduce/end support, is there enough community, and by community we really mean companies with investments they can't walk away from, to take over maintenance and ongoing development to maintain it as an sdk that can target the evolving platforms.
So whether Whirlpool or Toyota use Flutter is entirely irrelevant. You can maintain in-car systems on private code, evidenced by how that was historically done. Toyota using this as their sdk for in-car whatever doesn't help someone whose problem is they need Flutter to work well on ios/android.
Whirlpool building an ecommerce app for Brazil... golf clap. Same as MGM's app. Small teams built those; small teams can build new ones. who cares.
Even citing the whirlpool app, which is (link followed) actually this:
https://flutter.dev/showcase/whirlpool
built by a small outsourced company makes clear how thin the support actually is. Suppose google drops support: how many ft engineers is Whirlpool going to pay to maintain Flutter as a first-class deploy target? I'd bet zero.
There's nobody like, just for example, Shopify with a multi-billion dollar commitment and a history of open source work who has an investment they're stuck with. or Facebook. Google's internal ads doesn't count: they already Angular'd people. They're perfectly capable of maintaining that as a one-off internal sdk.
They don't use it for gmail/maps. Or anything where the migration costs start with a B.
[0]: https://docs.flutter.dev/platform-integration/bind-native-co...
[1]: https://docs.flutter.dev/platform-integration/platform-chann...
Literally every iOS developer under the sun will tell me that this is a good thing.
I certainly don't think having my app sticking out like a sore thumb, using a design language from old outdated iOS versions is "a good thing"
Seems like it requires 32gb of ram! Also Flutter is already very mature and can produce not only near-native mobile apps (the difference is almost negligible) but can target desktop and even web applications.
I do wonder how much of a boost skip offers vs Flutter's mobile apps. Will give skip a try when dram prices normalize.