71–80 of 97 posts
I like the idea of a single framework for all platforms and have always wanted to get into Flutter. Thee main barrier for me has been the Dart language, I wish it was written in a more popular language like Go.
You should give Dart a try, it's a lovely language. and very easy to pick up. In fact, it's become my favorite of the modern languages. For perspective, I come from a primarily Java/C# background, with large smatterings of Python, JS/TS, and Go, not to mention other less popular languages. I would describe it as C#-lite. It's got all the features of a modern C-derived language with very little of the accumulated comp…
- no value types
- missing fundamental integer types (eg. 64 bit unsigned integer)
- no data classes (records are anonymous)
- no tagged unions
- no static metaprogramming (macros coming soon)
- limited constructors (initializer list expression can't use earlier values in the list, no object initializers)
List is still too often used in APIs instead of Uint8List, even though it has 8x overhead.
Slower than C#, Java, Kotlin & Go. Performance is same as JS (even though it's statically-typed, AOT compiled language).
Flutter has three major problems: - Performance: Even on Desktop, animations have jank. Last I compiled samples on Mac, the problem was visibly there. - UX: Text editing immediately feels alien. If Mac for example, you have a text field in a native app and on the side you have a flutter app with a text field, you can tell the difference between the "feel" when you type in each. This isn't necessarily limited to text…
Fourth, it was never wanted from the Android team, with key figures like Jake Wharton having issues with it, "Flutter is a manifestation of everything wrong with Google as a company. A language that should have (and did) fail but kept alive. Control of the two most popular platforms on the planet and failing to unify them while allowing a third to be created that actively undermines both" https://twitter.com/JakeWhar…
Wrapping native controls often means being limited by a lowest common denominator in cross-platform scenarios.
Earlier quoted context omitted.
Fourth, it was never wanted from the Android team, with key figures like Jake Wharton having issues with it, "Flutter is a manifestation of everything wrong with Google as a company. A language that should have (and did) fail but kept alive. Control of the two most popular platforms on the planet and failing to unify them while allowing a third to be created that actively undermines both" https://twitter.com/JakeWhar…
Doesn't Jetpack Compose use native controls while Flutter implements its own controls? Wrapping native controls often means being limited by a lowest common denominator in cross-platform scenarios.
JetBrains is the one that decided to take it beyond Android.
Earlier quoted context omitted.
Doesn't Jetpack Compose use native controls while Flutter implements its own controls? Wrapping native controls often means being limited by a lowest common denominator in cross-platform scenarios.
Jetpack Compose is the new native controls framework for Android. JetBrains is the one that decided to take it beyond Android.
Do you think Jetpack Compose could be made multiplatform in Flutter's way (ie drawing its own controls on all platforms)?
Flutter has three major problems: - Performance: Even on Desktop, animations have jank. Last I compiled samples on Mac, the problem was visibly there. - UX: Text editing immediately feels alien. If Mac for example, you have a text field in a native app and on the side you have a flutter app with a text field, you can tell the difference between the "feel" when you type in each. This isn't necessarily limited to text…
This problem is mentioned whenever Flutter is discussed.It's been several years already. Seriously, they have a ton of smart people there, how it's not their number one epic? Unless, well, it's an architectural problem and nothing can be done - but then why continue the project at all?
Earlier quoted context omitted.
It is not a small niche at all. A ton of things are mobile first/only.
And plenty of well known companies have discovered that mastering two native stacks is still easier and cheaper in the long run, than mastering a "cross-platform stack" framework + dealing with leaky abstractions + build integration issues + having to master the native stack anyway. Either go mobile Web, or native.
They use Jetpack on Android
https://github.com/vector-im/element-x-android
And SwiftUI on iOS
https://github.com/vector-im/element-x-ios
But both use the same underlying Matrix Rust SDK
https://github.com/matrix-org/matrix-rust-sdk
So they share the core part of the app between platforms, but everything user facing is native
Earlier quoted context omitted.
Jetpack Compose is the new native controls framework for Android. JetBrains is the one that decided to take it beyond Android.
My mistake. I was thinking of Compose Multiplatform. Do you think Jetpack Compose could be made multiplatform in Flutter's way (ie drawing its own controls on all platforms)?
Shortcuts don't work, accessibility doesn't work, integration with OS workflows might not work, lags behind any OS updates, there is Look but no Feel.
Earlier quoted context omitted.
Flutter is mainly a mobile framework. Electron owns the desktop, anyone using flutter on the web is crazy. While you're points are valid, they are kind of irrelevant.
The marketing literature begs to differ. The Google's own Family Link app even on web[0] is also a Flutter app. [0]. https://familylink.google.com