My statement wasn’t merely about UI. It’s about a lack of respect for conventions. It’s about many things that are inherently wrong with Flutter’s pretend-to-be-native approach, which happens to include UI boondoggles.
Flutter would have been better off with an entirely separate UI convention and stop trying to pretend to be like native apps. I’d still hate it because it really adds nothing to the story that wasn’t in Java+Swing two decades ago, but at least they could start paying attention to how poorly Flutter apps work in their intended contexts instead of trying to keep up with the Joneses.
The abysmal macOS System Settings, with how it cribs from iOS design language, seems to be doing what Flutter is accused of. Though perhaps that is less the fault of SwiftUI, and more of Catalyst.
>Except you were posting on a sub-thread discussing the importance of those “tiny UI differences”.
Not true. The sub thread was about whether or not users can tell the difference between native and cross platform apps, specifically Flutter, and whether they care.
satvikpendem wrote this:
"Good for you, but most people can't tell nor do they care, given that I've shipped Flutter apps across thousands of users, both consumer and enterprise, whom we collect feedback from. Not once did anyone complain about the app visuals or performance itself"
The context is everything and anything that users could notice and provide feedback on, not just visuals.
Also, I think you may have missed the link in my argument between battery usage and the attempt to imitate native visuals.
Sigh … It's 2023 and somehow some people still don't know how to use internet discussion boards… Come on, you've been lurking in there for the past 16 years!
The original messages in the sub-thread [1] and the message you were responding to[2] were about UI/UX. Had you responded to the even higher level comment you are referring to[3], then you'd have been on-topic…
The same way, if you started to criticize Crux (the topic of the OP) at this point of the thread, you message would be completely off-topic as well.
I do not accept that discussing battery usage in a debate about cross platform technologies is-off topic just because the direct parent comment didn't mention it.
The parent comment claimed that users don't notice the difference between native and cross-platform. I responded saying that even if they didn't notice the visual difference, they will surely notice the battery drain directly caused by the attempt to achieve accurate visual parity.
This is not off-topic by any reasonable standard. This is merely addressing a closely related and very relevant aspect of the same topic.
Also, battery usage isn't a native vs portable UI toolkit thing, it's an issue when using Flutter but can also be an issue when using SwiftUI.