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

Google's cross-platform Flutter UI toolkit goes 1.0

techcrunch.com

Post reply on HN
Print view View original

91–100 of 343 posts

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#91

Post by coldtea »

jmull wrote: post #83

Cross-platform frameworks that don’t use native controls have suffered from problems... - They inevitably don’t look or work like native apps in ways both big and small, frustrating and annoying users. (... the spell-checker doesn’t work right or text selection is janky or unavailable where it should be, certain short-cuts work differently or have different gestures or keys, etc.) - they don’t get updates to native c…

>- They inevitably don’t look or work like native apps in ways both big and small, frustrating and annoying users.

We're way past that in the mobile world, where both Google, Facebook, and other top dogs use non-native cross platform frameworks and looks (e.g. Material UI).

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#92

Post by [deleted] »

mikece wrote: post #8
bluetidepro wrote: post #2

Congrats on their 1.0 launch! I haven't looked too closely at Flutter yet, to be honest. How does it compare to React Native (besides what a basic Google search will yield)? Has anyone jumped ship for either or after trying one of them?

Comparison: React Native (and Xamarin, for that matter) use platform-native widgets with JavaScript composing the UI dynamically in the case of React Native (and UI's either dynamically composed or statically compiled with Xamarin -- depends how you build the app). Flutter brings it's own widget layer to iOS and Android (and Fuchsia?) so it's more like starting with a blank 2D graphics canvas and creating your own co…

[deleted]

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#93

Post by dmix »

jmull wrote: post #83

Cross-platform frameworks that don’t use native controls have suffered from problems... - They inevitably don’t look or work like native apps in ways both big and small, frustrating and annoying users. (... the spell-checker doesn’t work right or text selection is janky or unavailable where it should be, certain short-cuts work differently or have different gestures or keys, etc.) - they don’t get updates to native c…

These are all excellent points. I'm curious how Flutter stands to address these risks/issues in the early days.

I'd imagine it will take much more than 1.0 to get close to parity with the OS. Even if we assume it will always be 90% of the full OS experience (which is fine for the vast majority of use cases).

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#94

Post by rapsey »

izacus wrote: post #74
pzo wrote: post #67

Writing plugins/bindings for native code in flutter doesn't look fun. Almost 100 lines of code to write binding for function that doesn't take any parameters and returns simple 'int' (int getBatteryLevel()). This just looks even worse than JNI to me. Don't want to even thing how long time it would take me to write bindings for function that do image processing. https://github.com/flutter/flutter/blob/master/examples/…

> We are on the verge of VR and AR and I don't see how flutter can help e.g. processing >100fps Video Feed using OpenCV library. The demo they presented on stage with ML and smile detection had quite big latency. I wouldn't call it real time. I can't find any claim from Flutter team that 100fps video processing is even their goal. So that's a strange metric to measure it by - especially since it's competing against J…

> On mobile? Qt really isn't pleasant or usable on mobile.

What's wrong with it?

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#97

Post by dman »

allenbrunson wrote: post #89
dman wrote: post #58

Any news on if the desktop embeddings will become a supported part of Flutter?

in today's keynote, google announced that you'll eventually be able to use one dart/flutter codebase for ios, android, mac, windows, linux, and the web. you can't get much more cross-platform than that.

I am aware that you can build one codebase for all those platforms, the question is whether all those platforms are supported. In particular https://github.com/google/flutter-desktop-embedding still says that desktop use of flutter is unsupported.

DISCLAIMER: Opinions expressed are my own and do not reflect my employers views.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#98

Post by forgot-my-pw »

lern_too_spel wrote: post #77
forgot-my-pw wrote: post #45

Earlier quoted context omitted.

Dart is being used internally at Google for AdWords and other core products: https://www.dartlang.org/community/who-uses-dart Even if it's not popular elsewhere, with its use inside Google, it won't be going away anytime soon.

AdWords previously used GWT, which is no longer maintained by Google. I get the feeling the AdWords team just really doesn't like JavaScript, which is understandable, but it doesn't say anything about whether AdWords will stick with the current non-JavaScript language du jour or move to another.

GWT served them well for 8 years. Now the Dart one is expected to last for the next 7+ years.

Read this interview if you're interested to learn more on their reasoning: https://news.dartlang.org/2016/03/the-new-adwords-ui-uses-da...

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#99

Post by kyrra »

lern_too_spel wrote: post #77
forgot-my-pw wrote: post #45

Earlier quoted context omitted.

Dart is being used internally at Google for AdWords and other core products: https://www.dartlang.org/community/who-uses-dart Even if it's not popular elsewhere, with its use inside Google, it won't be going away anytime soon.

AdWords previously used GWT, which is no longer maintained by Google. I get the feeling the AdWords team just really doesn't like JavaScript, which is understandable, but it doesn't say anything about whether AdWords will stick with the current non-JavaScript language du jour or move to another.

History here is a bit important. GWT existed before jQuery was a thing. GWT was created for 2 reasons (from what I can tell): remove cross-browser differences and simplify development for a team that was already using Java.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#100

Post by pjmlp »

thosakwe wrote: post #81
pjmlp wrote: post #60

Unless they force Flutter upon Android devs, I will let it pass, not eager to learn Dart.

It's strange to me that after all this time, every time a thread about Flutter reaches Hn or proggit, there are multiple comments about the choice of the Dart language. I think they've made it pretty clear by now that they don't have intentions of switching from Dart. Heck, they've published an entire "Why Flutter uses Dart" article explaining their reasoning. It's like beating a dead horse. Besides, you could always…

Their whole reasoning just feels like justification after fact. specially when one has experience with older development environments which offered similar developer workflows.

I guarantee to you that if they had choosen a proper modern language, Flutter's uptake would be much higher.

As it is, you will see many of us complain about Dart until Flutter ends up being replaced by something else, unless they force Android developers to actually use it.

Post reply on HN