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

341–350 of 780 posts

Re: Flutter 2

#341

Post by TheGuyWhoCodes »

throwaway123x2 wrote: post #293
blacktriangle wrote: post #132

Earlier quoted context omitted.

We're nagging because the apps suck and stick out like a sore thumb. Maybe Flutter will be the one to get there and be the holy grail of cross platform UI development, but the developer community has been burned by this promise so many times, we're going to have to see the final product before getting excited. Just because a project is ambitious doesn't mean we should all jump on board, particularly when similar proj…

Oof remember when PhoneGap was the next big thing? RIP

I remember big corps betting on phonegap and sencha for mobile 7 years ago. I also remember big corps betting on GWT.

Those were painful days...

Re: Flutter 2

#342

Post by mkl »

themacguffinman wrote: post #224
LocalPCGuy wrote: post #145

Earlier quoted context omitted.

In the context of the web, this seems like it should be a non-starter. Why should the developer be able to tell the user what can and cannot be selected?

They already can, CSS has a property called "user-select" that can be set to "none". It's pretty common to disable user selection on label text that isn't expected to be copied.

This is annoying, but is at least trivial to get around with browser debugging tools. The web developer is not the person whose expectations matter. Selecting label text is almost essential for being to explain to someone else how to do things, or communicate about the interface with the site developer.

Re: Flutter 2

#343

Post by andrewstuart »

opwieurposiu wrote: post #242
andrewstuart wrote: post #235

When a company releases a new technology for building desktop applications, the primary thing I look for is a really solid fleshed out implementation of a CRUD application: - sign in to some back end - create and edit data using forms - browse data in some sort of datatable/datagrid - use ajax to GET and POST data But such a demo is pretty much never there - I certainly can't see it in this case. But surely the vast…

Check out https://gallery.flutter.dev/ for a CRUD sample app.

Can you hone that down to a specific link showing the features listed?

Re: Flutter 2

#344

Post by ROARosen »

eseidelGoogle wrote: post #155
rp1229 wrote: post #127

Earlier quoted context omitted.

The new Google Pay app on iOS is incredibly sluggish -- animations stutter, switching pages has hesitations. I'm not sure what they mean by "quality" in this case.

[Flutter Eng. Dir here] We were also not satisfied with the performance of the initial GPay release. We've been working with the GPay team the last couple months and have made significant improvements within both Flutter and the GPay app. Hopefully the next release of GPay will be out soon and others will be able to see the progress we're continuing to make with the team.

> We've been working with the GPay team the last couple months and have made significant improvements within both Flutter and the GPay app

So seriously, how can you reassure any indie dev not getting VIP support to optimize their app for laggyness, that they can easily produce a decently performant app?

Re: Flutter 2

#345

Post by pvinis »

trezm wrote: post #27
tpmx wrote: post #2

Last time I tested a Flutter-built app on an iPhone X (perhaps a year ago) there was still obvious jank in transitions/animations. I assume most of the showcases mentioned here (WeChat, Grab, Yandex Go, Nubank, Sonos, Fastic, Betterment and realtor.com) are Flutter-based on Android only? Is there a well-built Flutter-based iOS app without jank now?

Interesting you mention it. I've actually been working on a fairly fully featured app in flutter, and was shocked at how well it performed on iOS. Coming from the React Native world its miles ahead in terms of perf, at least in our case. Shameless plug, the app is https://droppod.gg , an app to find time to play video games with your friends!

I like the idea so I just installed it. In the sign up screen I can swipe back and get to a second sign up screen, then swipe back again and I go to a loading screen forever.

I don't know if that's flutter or you, but it doesn't fill me with confidence.

Re: Flutter 2

#346

Post by sriku »

sriku wrote: post #339
eseidelGoogle wrote: post #98

Earlier quoted context omitted.

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

Sorry but the plasmadev demo doesn't pass muster compared to 60fps animations we were able to do years ago with html+js. Something about the renderer approach is causing hiccups in the animation. "Buttery smooth animations and scrolling" will be a great selling point for flutter ..if it actually works. (Firefox)

I'd say a goal of "do useful stuff extremely well and complex stuff reasonably well" would make for a good demo.

Re: Flutter 2

#347

Post by anthk »

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

> and it is janky as it can get, it feels like I'm using a 15 year old computer.

Ironically computers 15-20 years ago with native software ran much, much much faster and snappier. KDE3, XFCE, even Windows 98SE and XP were much faster. They were crippled by disk I/O, true, but once the software loaded, the feedback was inmediate.

Re: Flutter 2

#348

Post by jamil7 »

pier25 wrote: post #178
lostmsu wrote: post #146

Earlier quoted context omitted.

Flutter does not offer enough to justify learning new programming language.

Dart is extremely easy to pick up if you've written in any C style language. Someone in our team had a small Android TV app working in 2-3 days with WebSockets, web views, some animations, etc.

Yeah but it’s usefulness is really limited and just feels shoehorned into the project. Why couldn’t it have been Kotlin or TS? Something that mobile developers or web developers could jump into and keep a bunch of their existing tooling.

Re: Flutter 2

#349

Post by ttt0 »

eulers_secret wrote: post #218
whalesalad wrote: post #174

Earlier quoted context omitted.

Interesting rationalization. Don’t you think copying text is the norm and not the exception?

I do think it's the norm, and very much dislike this trend. I should make my position more clear: I hate this stuff with a passion. But, big business wants better content protection, and big money always gets what it wants - very few exceptions there. I wish we could do something as technologists who want to keep these features of the web; but against trillion dollar companies I know who I'd bet for...

It's the same argument as with DRM. I can just screenshot the text. It doesn't solve anything and only makes it painful for the average user.

Re: Flutter 2

#350

Post by heavyset_go »

hanniabu wrote: post #301
blacktriangle wrote: post #132

Earlier quoted context omitted.

We're nagging because the apps suck and stick out like a sore thumb. Maybe Flutter will be the one to get there and be the holy grail of cross platform UI development, but the developer community has been burned by this promise so many times, we're going to have to see the final product before getting excited. Just because a project is ambitious doesn't mean we should all jump on board, particularly when similar proj…

I don't understand why more resources aren't being put into Qt and making that easier to use or building a more "web-developer-friendly" abstraction layer on top.

Qt's QML + QtQuick follow the declarative and reactive programming paradigms and use JavaScript, and were released before React existed.
Post reply on HN