| ▲ | agentifysh 5 hours ago |
| This is a welcome addition but why should Flutter devs use this ? 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. |
|
| ▲ | marcprux 4 hours ago | parent | next [-] |
| See my response below on the KMP question: the comparison with CMP mostly applies to Flutter as well. > 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. [1] https://github.com/flutter/flutter/issues/170310 |
| |
| ▲ | IshKebab 3 hours ago | parent | next [-] | | > Flutter isn't going to be implementing these new interface conventions 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. | |
| ▲ | holoduke 44 minutes ago | parent | prev [-] | | Well sorry. But Android UI is bad just bad. The settings, the menus. Its bloated and almost as if they deliberately made it annoying to use. It just sucks. |
|
|
| ▲ | skavi 4 hours ago | parent | prev | next [-] |
| Dunno about Skip, but I can always tell when an app is Flutter. They feel like crap. Everything's a bit off with the native looking widgets. And fully custom designs still animate a bit weirdly. And they definitely still stutter. Somehow a tier below React Native. |
| |
| ▲ | winrid 4 hours ago | parent [-] | | Flutter re-generates the entire layout every tick and diffs it (immediate-mode), like a game engine. If your device isn't quite fast enough it'll lag, yep. RN is retained mode (but written in immediate-mode style and the diffing only happens when it has to). | | |
|
|
| ▲ | well_ackshually 3 hours ago | parent | prev | next [-] |
| Flutter is fine if you don't care about performance, accessibility, have no need to access native capabilities or non-fluttered widgets (ex: the Google map integration is awful) and overall just want to make an internal app. 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. |
| |
| ▲ | elemdos 2 hours ago | parent | next [-] | | That sounds like the worst parts of native dev + PWAs combined | |
| ▲ | x0x0 2 hours ago | parent | prev [-] | | And are comfortable making a 1-2 million dollar per devteam per year bet that Google won't rug pull you. And they seem to have no important or big app on it. On an unrelated note, in 2024 Google did layoffs on the Flutter team. |
|
|
| ▲ | trevor-e 4 hours ago | parent | prev [-] |
| Flutter still doesn't support liquid glass on iOS so it doesn't seem like a serious contender to me at this point. And due to the nature of how Flutter is implemented, it's going to continuously be an uphill battle. Maybe it's fine if you intend on having a completely custom UI and don't care about platform look and feel. |
| |
| ▲ | eptcyka 3 hours ago | parent | next [-] | | > Flutter still doesn't support liquid glass on iOS Literally every iOS developer under the sun will tell me that this is a good thing. | | |
| ▲ | daveidol 2 hours ago | parent | next [-] | | Why? I'm an iOS developer and, while I don't love everything about liquid glass, that is the current design language of iOS. 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" | |
| ▲ | frizlab 3 hours ago | parent | prev | next [-] | | No. I’m an iOS developer and will not tell you that, except to say it’s a good thing to have one more reason for the people not to use flutter. | |
| ▲ | lawgimenez an hour ago | parent | prev [-] | | That’s not a good thing if you don’t adapt liquid glass. I’m an iOS developer. |
| |
| ▲ | cosmic_cheese 4 hours ago | parent | prev | next [-] | | In general, the "render UI as if it were a video game" route feels like a bit of a dead end on mobile to me. On desktop it's more workable but still isn't without issues. | |
| ▲ | skybrian 3 hours ago | parent | prev [-] | | I've heard bad things about liquid glass and plan to skip that OS release, so not implementing it seems like an advantage from my perspective. |
|
