Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flutter 2

developers.googleblog.com

Post reply on HN
Print view View original

71–80 of 780 posts

Re: Flutter 2

#71

Post by hobofan »

timsneath wrote: post #51
fwip wrote: post #39

Earlier quoted context omitted.

The example spinner ( h https://flutter.dev/#dartpad-landing-page ) also looks pretty choppy on my Macbook Pro 16. I haven't tried on lower-specced devices, but it doesn't inspire a lot of confidence.

Yeah, that's running in development mode, since it's a scratchpad for live coding. Try something like https://flutterplasma.dev for an example of Flutter's web support when compiled in release mode.

Yeah, that's still not great on a Macbook Air 2014. I'd even say that the spinner at the end looks even choppier.

Re: Flutter 2

#72

Post by krasin »

timsneath wrote: post #51
fwip wrote: post #39

Earlier quoted context omitted.

The example spinner ( h https://flutter.dev/#dartpad-landing-page ) also looks pretty choppy on my Macbook Pro 16. I haven't tried on lower-specced devices, but it doesn't inspire a lot of confidence.

Yeah, that's running in development mode, since it's a scratchpad for live coding. Try something like https://flutterplasma.dev for an example of Flutter's web support when compiled in release mode.

Thanks for the link. To confirm the point of copying text being broken: try doing that at https://flutterplasma.dev/ -- it kind of works, but not really, no.

Re: Flutter 2

#74

Post by eseidelGoogle »

beaner wrote: post #28

> Google Pay switched to Flutter a few months ago for their flagship mobile app, and they already achieved major gains in productivity and quality. I don't know how they can claim this. The new Google Pay on Android was noticeably laggier the moment it was released. It continues to be so, and I still hate using it. Now I know the cause.

[Flutter Eng. Dir here]

The initial GPay Flutter release definitely had some performance rough spots. We've learned a lot from working with that team since release and have made resulting changes in both Flutter and the app code.

GPay hasn't released since December last I checked, but I expect the next release should perform better on both iOS and Android and we will be continuing to work with them closely over the coming months.

Re: Flutter 2

#75

Post by colesantiago »

This is HUGE, an absolute game changer in the cross platform space and in competing with electron, my congrats to the flutter team on this release.

I anyone using Flutter in production currently?

Re: Flutter 2

#76

Post by underwater »

beaner wrote: post #28

> Google Pay switched to Flutter a few months ago for their flagship mobile app, and they already achieved major gains in productivity and quality. I don't know how they can claim this. The new Google Pay on Android was noticeably laggier the moment it was released. It continues to be so, and I still hate using it. Now I know the cause.

I had wondered what had happened to this app to make it so slow. It takes around 10 seconds to get past the loading screen and show me anything useful on an S9.

Those seconds are excruciating when I'm at a checkout trying to actually use the app, with a large line behind me and a checkout person staring at me.

Re: Flutter 2

#77

Post by gtirloni »

belinder wrote: post #12

So how does it run natively on desktop? Is it like electron? Can't tell from the linux example

The docs[0] are pretty good. It looks like there is a concept of "embedder" that does the hard work. See [1].

0 - https://flutter.dev/docs/resources/architectural-overview

1 - https://github.com/flutter/flutter/wiki/Custom-Flutter-Engin...

Re: Flutter 2

#78

Post by dstaley »

refulgentis wrote: post #66
dstaley wrote: post #7

Flutter for Web feels like such a wild step backwards in terms of functionality that I'm not sure the benefits it brings are worth it. I just tried a few samples, and basic interactions like selecting text, saving images, and opening links in new tabs don't work. This is the result of rendering everything to a element. I'm much more interested in a React Native style approach, which seems to provide a consistent set…

Things changed a lot, I observed the same symptoms as late as late 2020, I can't reproduce these issues now In general Flutter for Web is _amazing_ if you want to deploy an app. after seeing this thread, pretty clear to me its almost a perfect nerdsnipe - makes perfect sense if you're already building a Flutter codebase, sounds bonkers if you build web apps.

Check out Flutter Folio [1], built in partnership with Google. Right-click is actually disabled, so you can't even open the "Create account" link in a new tab, nor can I right click an input to autofill with my password manager. You can't inspect any image rendered to the canvas element. Furthermore, you also can't blur the form input (although that's probably application specific rather than Flutter's fault).

[1] https://www.flutterfolio.com/#/?

Re: Flutter 2

#79

Post by dhbradshaw »

dstaley wrote: post #7

Flutter for Web feels like such a wild step backwards in terms of functionality that I'm not sure the benefits it brings are worth it. I just tried a few samples, and basic interactions like selecting text, saving images, and opening links in new tabs don't work. This is the result of rendering everything to a element. I'm much more interested in a React Native style approach, which seems to provide a consistent set…

They were pretty clear about the intention here: make the web available as a platform for running mobile and desktop-style apps.

If you're trying to create a classical website, it's not the right tool. Use html and css. If you're trying to make a rich app, I'd bet on Flutter.

I'd be interested in seeing it become easier to make a combination of the two -- flutter apps embedded in classical websites.

Re: Flutter 2

#80

Post by timsneath »

tshaddox wrote: post #34
dstaley wrote: post #7

Flutter for Web feels like such a wild step backwards in terms of functionality that I'm not sure the benefits it brings are worth it. I just tried a few samples, and basic interactions like selecting text, saving images, and opening links in new tabs don't work. This is the result of rendering everything to a element. I'm much more interested in a React Native style approach, which seems to provide a consistent set…

Yeah, I haven’t been following Flutter, but I’m surprised their approach to the web is just shipping their entire custom layout/drawing code in WebAssembly and drawing everything with canvas. I would have expected them to actually port their native UI components (buttons, links, text, etc.) to their corresponding native components on the web, and maybe ship a custom layout engine if CSS layouts aren’t flexible enough…

We actually have two distinct approaches: the CanvasKit/WebAssembly approach you mention for high-intensity graphics, and an HTML-based renderer for other apps. This article has more details: https://medium.com/flutter/flutter-web-support-hits-the-stab...

You're right -- we do render the controls, so that existing Flutter code (that might itself include custom styling or matrix transforms) just runs without change or surprise, but we integrate with the underlying browser support for things like text autofill and accessibility.

Post reply on HN