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

91–100 of 780 posts

Re: Flutter 2

#91

Post by kevincox »

kureikain wrote: post #50

I want to love Flutter. But once looking at it, it's a no go. It's the new flash. Really, you cannot copy the text anymore. React native is my goto solution now.

Yup. I would also like to open links in new tabs, view images, copy links, search on page, use browser extensions...

I can see it being useful for games and similar where there isn't really any UI but even then I would want dialogs and similar to use regular text that I can copy.

I am definitely not looking forward to flutter on the web. I foresee a lot of websites that I will need to avoid.

Re: Flutter 2

#92

Post by DodgyEggplant »

bilal4hmed wrote: post #48
ahmedfromtunis wrote: post #36

This is definitely interesting; I'm so tempted to try this. But the question that comes to mind with this kind of the technology from Google: is there any mandatory Google services that I'd have to use? Just as an example: Do I have to use Google's ad platform or I can use any other service?

you dont have to use any google services to work with flutter.

for now

Re: Flutter 2

#93

Post by agumonkey »

baybal2 wrote: post #37
tshaddox wrote: post #34

Earlier quoted context omitted.

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…

Gtk tried the same with broadway. It went nowhere.

Well they made libreoffice run in canvas IIRC, which is quite somewhere :D

But yeah it's not grabbing market share that's for sure.

Re: Flutter 2

#94

Post by merrvk »

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…

Yep, I’ve been really impressed with react native on the web so far. Our current code base deploys across Android, iOS, web and windows with minimal effort.

Re: Flutter 2

#95

Post by nullifidian »

Keyframe wrote: post #55

I haven't really looked, apart from glancing, into flutter yet. Now with desktops and mobile, premise seems interesting. How and does it compare to Qt?

I'm not sure, but I think that you have to use Dart language to use Flutter.

Incidentally, I was pretty sure that Dart was dead. Turns out it's alive. I'm not sure what it is currently, now that it's statically typed, null safe and all. What are Dart's killer features?

Re: Flutter 2

#96

Post by etaioinshrdlu »

randomchars wrote: post #35

The idea sounds very appealing, especially to an indie developer: being able to ship your app on multiple platforms from a single codebase is kind of the holy grail. Unfortunately, the result is.... I tested this Flutter example[1], on a 16" MBP with and i7, and it is janky as it can get, it feels like I'm using a 15 year old computer. From the code it looks like the whole thing is... rendered on canvas? I'll pass. […

I think this particular demo might also just be a badly designed demo.

Re: Flutter 2

#97

Post by matchbok »

eseidelGoogle wrote: post #82
gareim wrote: post #20

Earlier quoted context omitted.

Google Pay on the iPhone XS had so much jank and UI lag when I last used it a month ago.

[Flutter Eng. Dir here] I replied above as well. My team has also not been satisfied with the performance of the GPay app on all devices. We've been working with the GPay team since release and made many improvements in both Flutter and the GPay app. I expect there will be an updated GPay app soon, with still more performance improvements in the pipeline.

Why can't y'all just fix Android development instead of this flutter stuff that will be deprecated and killed off in 2 years because nobody uses it?

Re: Flutter 2

#98

Post by eseidelGoogle »

sydd wrote: post #87
mda wrote: post #64

Earlier quoted context omitted.

Well, to give counterpoint, just tested on Chrome / Windows (ok-ish CPU, decent GPU) all demos are buttery smooth no lag or jank whatsoever.

I've tested on my phone (1yr old pretty good Android one) and the whole thing is very laggy runs with like 10fps. What about a11y? The whole thing feels like Adobe Flex in 2010. It solves a great deal of problems that the web had but introduced a plethora of others.

[Flutter Eng. Dir. here]

Still relatively early days for Flutter Web, so I would not be shocked if it's not buttery everywhere. However, we would certainly love to learn more. fluter.dev/support has links as to how to file an issue if you're interested.

https://flutterplasma.dev/ is one demo to try. We expect to be updating flutter.dev/web and flutter.dev/showcase to update more over time.

Re: Flutter 2

#99

Post by matchbok »

What a mess - just make Android better please. Nobody uses this or wants to learn a new way of building apps. Swift and Kotlin are 100x better.

Re: Flutter 2

#100

Post by ddevault »

randomchars wrote: post #35

The idea sounds very appealing, especially to an indie developer: being able to ship your app on multiple platforms from a single codebase is kind of the holy grail. Unfortunately, the result is.... I tested this Flutter example[1], on a 16" MBP with and i7, and it is janky as it can get, it feels like I'm using a 15 year old computer. From the code it looks like the whole thing is... rendered on canvas? I'll pass. […

It is very janky, and worse, totally unaccessible, rendering it useless (or frustrating at best) for huge numbers of the population. And why? It's just yet another shiny web framework. We've known how to build websites for decades now.
Post reply on HN