Live data from Hacker News

We're forking Flutter

flutterfoundation.dev

551–560 of 748 posts

Re: We're forking Flutter

#551
post #326

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

It really feels like an "HN bubble" type argument, I've literally never heard it outside of HN.

Re: We're forking Flutter

#552
post #477

Earlier 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.

Typically people just make the app look and work the same in all platforms, like how you might expect a responsive web app to be like; no one is implementing Notion with a platform specific UI, for example, using Apple stuff on Apple devices or Windows stuff on Windows devices.

Re: We're forking Flutter

#553

Earlier quoted context omitted.

Unfortunately, not talking about that.

Don't elaborate or anything.

I think they're referring to the extra frame of latency when scrolling on Android. But then again, I've literally never heard anyone complain about that, I honestly don't think anyone notices, I believe the GitHub issue had to use a slow motion camera to even capture the issue.

Re: We're forking Flutter

#554
> 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!

Given 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

#555

Earlier 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.

I think people might be talking past each other on this issue. If you are on one platform only, then yes having apps behave the same is nice for muscle memory. However, if you're using multiple devices and platforms, then I want Slack to work the same regardless of device, I don't want iOS native navigation on the iPhone and Windows native navigation on the laptop.

Re: We're forking Flutter

#556
post #280

Earlier 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…

Flutter Web is for web apps, not web sites, so much of those concerns don't necessarily apply. And it's not "impossible" simply because Chrome itself runs on Skia which until recently Flutter did too, so clearly they were able to implement scrolling at least one time correctly.

Re: We're forking Flutter

#557
post #120

> 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.

Canonical is contributing to desktop and is using Flutter for a lot of their desktop components now.

Re: We're forking Flutter

#558

This 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…

Wrong analogy.

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

#559

Earlier 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).

It's only for the Indian market. As Google often does, they released Google Wallet for the US market. But that's not a failure of Flutter itself of course, only internal Google politics.
Post reply on HN