Earlier quoted context omitted.
The trouble with this is most users only use one platform and so don't care. They just see the app as badly implemented as it does not match other apps on the platform.
I used to think this, now I think nobody cares except people "in the know" Every time I've ever mentioned it to anyone they really didn't seem to understand or care
We're forking Flutter
551–560 of 748 posts
Re: We're forking Flutter
#552Earlier quoted context omitted.
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
> but I know that's down to the developer so I won't hold that against Flutter. That is absolutely an issue with Flutter, which throws away the underlying platform UX and draws to a canvas. It gives you relatively few tools to target "native look" controls for each platform without maintaining multiple UIs in parallel composed of entirely different widgets.
Re: We're forking Flutter
#553Earlier quoted context omitted.
Unfortunately, not talking about that.
Don't elaborate or anything.
Re: We're forking Flutter
#554Given that you could probably make a similar assertion about any popular framework, this doesn't strike me as particularly relevant.
Re: We're forking Flutter
#555Earlier quoted context omitted.
> but they don't fit in. You seem to say this like it's a bad thing?
I think it is, personally. Mostly because common UI appearance and paradigms makes software easier to use, especially for non-technical users. But in this specific instance I was referring to OP’s claim that it’s impossible to identify many Flutter apps, which I dispute.
Re: We're forking Flutter
#556Earlier quoted context omitted.
flutter's custom canvas render on web means so much of the web stops working or is slow. type anything non ASCII like an emoji or CKJ and eat while it downloads a font. No other pages do this. Text fields are missing all the standard context menu options like define, translate, etc... Things that would be selectable on any other page are not, etc....
If you care about the web at all as a target, you must not use Flutter. It’s awful. They used to have a DOM renderer which you could use and everything would be fine, but apparently no one used it because it wasn’t perfect, and they’ve recently deprecated it and will remove it sooner or later—they’re doubling down on the pure-canvas direction where it’s completely impossible to produce a good result. And I do mean im…
Re: We're forking Flutter
#557> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…
I can’t imagine using Flutter for desktop development if only because like most newer UI frameworks, it’s mobile focused and doesn’t come with important desktop widgets like tableviews/datagrids and treeviews.
Re: We're forking Flutter
#558This is a kind of a strange argument: >How large is the Flutter team, today? Google doesn't publish this information, but my guess is that the team is about 50 people strong. >That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! It's like claiming that the inventor of penicill…
It's claiming that people who produce penicillin, are responsible for billions of people who take penicillin.
That's a fair claim.
Re: We're forking Flutter
#559Earlier quoted context omitted.
I worked on the GPay flutter rewrite and our standard for accessibility was higher than almost any other app I've seen, and was a significant amount of effort spent on that. What accessibility shortcomings does flutter have?
This may be a silly question, but how do I install the Google Pay app on my iPhone? I'd like to try it out since it's the first app listed in the Flutter Showcase, people keep mentioning it in this thread, and it probably works as well as a Flutter app can, given that it's first-party from Google. But when I search for it on the App Store, it's nowhere to be found (or at least not in the first 20 results).
Re: We're forking Flutter
#560https://discourse.ubuntu.com/t/refreshing-the-ubuntu-desktop...