Live data from Hacker News

Ready for Production Apps: Flutter Beta 3

developers.googleblog.com

61–70 of 107 posts

Re: Ready for Production Apps: Flutter Beta 3

#61
post #11
post #10

Earlier quoted context omitted.

Being agree with all 4 points I see two drawbacks: 1. Not using OEM widgets. Even the rendered widgets may look good, they can't beat the native widgets optimized for the particular platform. 2. The choice of Dart as the main language. I can understand both points though

I don't think using non-OEM widgets is a bad thing because it's not like Electron; Flutter uses Skia to render widgets, and it's fast. There is an article https://medium.com/flutter-io/why-flutter-doesnt-use-oem-wid...

From the article:

> In other words, in today’s market, a branded, custom UI is king.

Does a custom UI per app not make it more difficult for people to learn each new app? Didn't the platform developers write their human interface guidelines for a reason? Or was that level of consistency only necessary in the early days of Mac and Windows, when the temptation was to port a DOS app straight over rather than redesigning it as a GUI?

Re: Ready for Production Apps: Flutter Beta 3

#62
post #35

Earlier quoted context omitted.

Dart has a VM (with hot reloading) for dev time and an AOT compiler for release builds. I’d say that’s one of the most attractive things about Dart to compensate for yet another language.

How large and invasive is the Dart runtime though? Running in a VM and running with a runtime are only so far apart. And I'm interested in distribution package sizes too.

Here is some info: https://flutter.io/faq/#how-big-is-the-flutter-engine

Re: Ready for Production Apps: Flutter Beta 3

#63
post #45

Apple really need to react if they want swift to get any traction. IOS hasn’t had any major UI update since iOS7 , and android is a mess anyway, so using a cross platform now makes more sense than ever. The icing on the cake would be to have a path for reusing dart business layer between flutter and angular. That’s a really promising stack.

You might be interested in this talk [1] from Dart Conf that highlights code sharing between Flutter and Angular Dart. The general take-away is that code sharing is possible, it requires however a strict separation of UI related and business logic code.

[1] https://m.youtube.com/watch?v=PLHln7wHgPE

Re: Ready for Production Apps: Flutter Beta 3

#64
post #46

Fun fact: on pre-release Angular 2 versions, Dart was it's main language. My hypothesis is that, if they decided to continue using Dart, probably we would have more Dart developers and this could have lead to a faster Flutter adoption.

angulardart (1) is still available, but probably not used by any serious project. Still have mixed feelings about dart - apparently some of the biggest frontends at Google (advertising) use this, so it must do something really good. 1: https://webdev.dartlang.org/angular

I've heard some pretty bad things about it from googlers

Re: Ready for Production Apps: Flutter Beta 3

#65
post #46

Fun fact: on pre-release Angular 2 versions, Dart was it's main language. My hypothesis is that, if they decided to continue using Dart, probably we would have more Dart developers and this could have lead to a faster Flutter adoption.

angulardart (1) is still available, but probably not used by any serious project. Still have mixed feelings about dart - apparently some of the biggest frontends at Google (advertising) use this, so it must do something really good. 1: https://webdev.dartlang.org/angular

I'm not sure what you mean?AdWords uses AngularDart. It's the best-supported way to build a web app in Dart.

There was web UI framework churn in Dart's early years, but last I heard, Google has settled on AngularDart.

Re: Ready for Production Apps: Flutter Beta 3

#66
How does it compare to React-Native?

I know it compiles to native, but on the other hand only the business-logic in RN is written in JS, UI and bindings are native.

Create-React-Native-App and Expo already deliver very good UX.

My main pain points with CRNA/Expo are bundle size and in-app purchases, not performance or DX.

Re: Ready for Production Apps: Flutter Beta 3

#67
post #11

Earlier quoted context omitted.

I don't think using non-OEM widgets is a bad thing because it's not like Electron; Flutter uses Skia to render widgets, and it's fast. There is an article https://medium.com/flutter-io/why-flutter-doesnt-use-oem-wid...

From the article: > In other words, in today’s market, a branded, custom UI is king. Does a custom UI per app not make it more difficult for people to learn each new app? Didn't the platform developers write their human interface guidelines for a reason? Or was that level of consistency only necessary in the early days of Mac and Windows, when the temptation was to port a DOS app straight over rather than redesigning…

Platforms also like their branded, custom UIs. When you build an app that uses the platforms widgets, you reinforce the platform's brand. When you use the same look everywhere, on the web and for apps on each platform, you reinforce your own brand.

If platform developers cared so much about consistency, they wouldn't change their UI design just to freshen up their image or because design trends have changed. Maybe looking and behaving like everyone else really has a major influence on user adoption, but it usually seems to be ignored in favor of branding.

Re: Ready for Production Apps: Flutter Beta 3

#68
post #23
post #21

Earlier quoted context omitted.

You don’t have to reload manually. Reloads automatically, make sure you have turned on reload on save in vs code or something similar in IntelliJ.

I see. I am using vim + commandline.

You could try writing a shell script using inotifywait to look for changes and then notify the program that it needs to reload the code.

Re: Ready for Production Apps: Flutter Beta 3

#70
post #45

Apple really need to react if they want swift to get any traction. IOS hasn’t had any major UI update since iOS7 , and android is a mess anyway, so using a cross platform now makes more sense than ever. The icing on the cake would be to have a path for reusing dart business layer between flutter and angular. That’s a really promising stack.

Ha. This is hilarious. Most high-profile / successful iOS apps (other than games) are native. And judging from what I’m seeing in the ecosystem, I’d guess that most teams out there have switched to Swift or will do so soon. There’s very little enthusiasm or innovation in the Objective-C ecosystem at this point. The lack of a major UI update in the last few years is a feature, not a bug. It doesn’t seem to have held b…

I don't think you got my comment right. I was advocating for apple to expand swift to other platforms ( android, pc desktop, web, server, whatever), in order to compete with techs like flutter.

The reason cross platform tools weren't a good fit before and are now is both because hardware is now powerful enough, and because platforms have now reach a stable point.

Post reply on HN