Live data from Hacker News

Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

developers.googleblog.com

51–60 of 467 posts

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#52
post #38

Has Flutter solved its footprint-bloat problem? The internet is littered with reports of 10-100MB+ .ipa and .apk binaries coming out of simple Flutter apps for iOS + Android. Google states they can't imagine the footprint ever dropping as low as 1MB. [1] On Web, 1MB of base runtime is a complete showstopper. Embedded applications may suffer similarly. Does today's announcement mean Google has figured out how to fix t…

'main.dart.js' in the example Flutter KENKEN app linked in the blog post: Chrome - 359kb Firefox - 990k I agree that Chrome is becoming more and more a proprietary channel for Google products, which is probably what its original intent was all along.

That's a very large payload difference indeed!

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#53

I’ve given Flutter a try with one of my client’s apps, and in some cases, it’s obviously better than native development. Mainly because you can develop for both platforms. I’d be curious to hear where other developers think Flutter is a good framework to use instead of developing native code.

On iOS it's obvious it uses emulated controls. I think if you want a fully themed app that looks the same across all environments, you should go with Flutter. If you want an app that looks the same as other native apps on the target environment, you should go with React Native.

(I'm the Flutter TL)

If you can tell that we're not using OEM widgets, we consider that a bug. Please file it and explain what the difference is. We're definitely not perfect, but fidelity is a high priority for us this year.

https://github.com/flutter/flutter/issues/new?template=BUG.m...

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#55

I wonder if the Flutter engine would work on a Linux system that has only 128MB or 256MB? I've been playing around with devices like this https://www.ebay.com.au/itm/WiFi-Display-Dongle-1080P-Wirele... and it would be fun to run Flutter engine on them. edit - would also be fun on the 4GB RAM rk3399 http://rockchip.wikidot.com/rk3399 tv box: https://www.ebay.com.au/itm/X99-TV-BOX-4K-UHD-RK3399-4GB-32G... open source L…

That Rockchip has an ancient Mali 400 GPU (with no open source drivers) that won't be able to render a Flutter app at 1080p, or lower even.

The engine library alone is also already ~70 MiB. Running the Flutter Demo on my RPi3 (in aarch64, so the numbers are somewhat inflated) it's at 250 MiB of memory (with about 60 MiB of that for the system) and an additional 60 MiB of graphics memory. This is on a 1366x768, where the RPi graphics just about manage 60 fps (when warmed up).

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#56

Flutter for Web is heavily reminiscent of Famous with its custom layout system and off-DOM rendering (or guessing DOM rendering support w/ CSS transforms of divs). To see, just view-source on the NYT demo. Quite divergent from the web platform in my opinion. The fact that they have to re-implement copy and paste (and, accessibility features!) further adds to that: https://medium.com/flutter-io/bringing-flutter-to-the…

God, I totally forgot about Famous. That was honestly one of the weirder things I’ve seen in my years of web development. Such a gorgeous website and yet I never really understood what they were trying to sell me on.

So much marketing, such little end result....never went anywhere, never amounted to anything meaningful.

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#58
post #29

Earlier quoted context omitted.

As a user, I care quite a bit. As a developer, though, I get paid to tell people that their software doesn’t follow platform UI conventions and I run their code through mental checklists (“does the title animate properly during a controller pop, does this custom view break accessibility”) so I think it’s pretty obvious that I have a very specific slant on this issue. Keeping that in mind, I think that many users do c…

Slant is putting it mild - you gotta start putting a disclosure in these kinds of comments or something. You were a WWDC scholarship recipient, interned at Apple, and seem to base your career on Apple tech. You are not a typical user, you will notice things most ordinary people would never think to notice. The vast majority of apps on a phone aren't even kept open by a user long enough for it to matter. I say this as…

> You were a WWDC scholarship recipient, interned at Apple, and seem to base your career on Apple tech.

I dabble in Android and Linux as well ;)

> You are not a typical user, you will notice things most ordinary people would never think to notice. The vast majority of apps on a phone aren't even kept open by a user long enough for it to matter.

Agree on both counts, but I like to think that users aren't completely clueless. There are certain things that they do feel acutely: animation physics that differ from the system's (particularly for things like scrolling), lag, choppiness, lack of proper accessibility support…

> There's increasingly little reason to bother with the stack.

I disagree with this (this isn't just an iOS thing, by the way: I would say the same for every other platform I've interacted with). It is almost certain to be the case that the team that wrote the platform libraries is smarter, better, and cared more than you did about the UI (there are some very notable exceptions, but I think it's very obvious when this is the case). Going with the native stack means lock-in and sometimes more work, but in exchange you get a significant amount of functionality "for free" (sometimes without even realizing that this functionality existed) and automatically share a common design language with the rest of the system, which is a usability plus for users almost all of the time.

Re: Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop

#60

Has Flutter solved its footprint-bloat problem? The internet is littered with reports of 10-100MB+ .ipa and .apk binaries coming out of simple Flutter apps for iOS + Android. Google states they can't imagine the footprint ever dropping as low as 1MB. [1] On Web, 1MB of base runtime is a complete showstopper. Embedded applications may suffer similarly. Does today's announcement mean Google has figured out how to fix t…

to be fair even angular has sizing problems. a "simple" app can easily grow to over 200kb gzipped content (including polyfills). and 200kb is a lot for a simple application.

currently our "big" application already grown to over 600kb gzipped js. I'm pretty sure flutter has the same problem. I think as soon as people start using a SPA their js size will skyrocket.

Post reply on HN