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

1–10 of 343 posts

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

#3

Post by fredgrott »

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?

someone did a performance test on android react vs flutter vs native app see https://robots.thoughtbot.com/examining-performance-differen...

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

#4

Post by pvinis »

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?

I'm guessing most answers will be about Dart being the hard pill to swallow for most, and the fact that it render by drawing UI instead of orchestrating like React Native.

I still prefer RN, and I don't my opinion changing in the future. I prefer controlling a native view for the apps I make. Maybe a game would be easier with Flutter?

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

#5

Post by bsimpson »

Flutter renders the whole UI, like a game engine. In the past, this has meant that if there isn't a Flutter implemention of a component (like a video player or map), you couldn't add it to your app. I don't know if that's still true.

[edit]: It looks like this has been addressed with the PlatformView widget: https://developers.googleblog.com/2018/12/flutter-10-googles...

[edit]: Sorry, bluetidepro - this was supposed to be a reply to you.

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

#6

Post by pier25 »

bsimpson wrote: post #5

Flutter renders the whole UI, like a game engine. In the past, this has meant that if there isn't a Flutter implemention of a component (like a video player or map), you couldn't add it to your app. I don't know if that's still true. [edit]: It looks like this has been addressed with the PlatformView widget: https://developers.googleblog.com/2018/12/flutter-10-googles... [edit]: Sorry, bluetidepro - this was supposed…

> like a game engine

In this aspect it's very similar to Flash or QT.

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

#7

Post by hbhakhra »

bsimpson wrote: post #5

Flutter renders the whole UI, like a game engine. In the past, this has meant that if there isn't a Flutter implemention of a component (like a video player or map), you couldn't add it to your app. I don't know if that's still true. [edit]: It looks like this has been addressed with the PlatformView widget: https://developers.googleblog.com/2018/12/flutter-10-googles... [edit]: Sorry, bluetidepro - this was supposed…

They just addressed this in today's announcement:

As for new Flutter features, Google today announced ‘Add to App,’ a new feature that makes it easier for developers to slowly add Flutter code to existing apps. In its early days, Flutter’s focus was squarely on building new apps from scratch, but as it has grown in popularity, developers now want to use it for parts of their existing applications as they modernize them.

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

#8

Post by mikece »

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 controls. Advantages: since this rendering layer and widgets are compiled from C++ the performance is excellent. Disadvantage: if you want a widget that isn't in the current set of controls and your C++ skills aren't up to the task, you'll be left wanting to do things you cannot. Not sure what scenarios are affected by this but it's something to keep in mind.
Post reply on HN