Hacker News new | past | comments | ask | show | jobs | submit login

I love the idea of Flutter for mobile and desktop but I'm very skeptical about the web implementation.

They will need to reimplement tons of stuff that are already included in the browsers and ship all that code with the application.




I look at it differently. When someone compiles a game to webassembly it's seen as an accomplishment, right?

It doesn't mean you would normally write web apps this way, particularly if you're targeting consumers internationally and need web pages to load fast.

But being able to make a desktop or mobile app work in a browser should be useful, particularly for businesses. Sometimes you're not targeting the whole world and can assume users are office workers who have a reasonably fast desktop-class computer and a decent network connection. (Or if they're away from the office, they've already installed the mobile app.)

Some markets are more sensitive to download size than others and you need to understand your users to know what you can get away with.


> When someone compiles a game to webassembly it's seen as an accomplishment, right?

Yes, but browsers do not have game engine APIs. They do however have a layout engine, text editing and rendering, accessibility features, and a very long etc. Basically anything you need to make an app with text, images, buttons, etc.

Don't me wrong, I'm sure Flutter for the web is a technical marvel.

> Some markets are more sensitive to download size than others and you need to understand your users to know what you can get away with.

So you are arguing that Flutter for the web is a nice bonus you get but not really intended to be a general use case web dev framework.

If this is the case, it seems the Flutter team is missing a huge opportunity by not being a truly universal UI toolkit which it could be if it used the DOM instead of reimplementing everything.


I don't know what it's intended for or who will find it useful. Just saying that it's not a binary choice (either useful or useless for everyone).


> Sometimes you're not targeting the whole world and can assume users are office workers who have a reasonably fast desktop-class computer and a decent network connection.

Maybe. Just don't make any assumptions about their physical abilities, i.e. make sure business apps are accessible unless the task at hand inherently assumes a particular ability (i.e. is inherently visual).


Very well said! Thank you!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: