3 ms·
The main value is to target multiple platforms at once. Otherwise there's no point in choosing Flutter to develop for the web.
by BenGosub 6y ago
The main value is to target multiple platforms at once.
Otherwise there's no point in choosing Flutter to develop for the web.
- deleted 6y ago[deleted]
- nexuist 6y agoAs someone who shipped an app in Flutter on Android and iOS, there is practically 0 code re-usability between web and mobile. Regardless of platform, mobile apps feel the same - they both have navbars, tab bars, lists and table views, etc. Even if I could use an iOS navbar on web, it would look so out of place it's not worth considering. Okay, so you can't reuse UI components, surely you can reuse the Dart code that makes up the guts of the webapp? And, sure, you could, but why would you when you can spend maybe 10 minutes to translate it to native JS (the two languages are practically identical) and ship it without the Flutter Web dependency? I actually feel like it'd be easier for me to convert some of my Flutter components into React ones, than to try and learn Flutter Web and set up its whole toolchain. I think it's a cool idea, but it's not meant for widespread use (speculation): it's meant specifically for Google's Fuchsia, where they are probably planning on shipping Web applications pretending to be native desktop apps along with the full Chrome experience much like they did for Chromebook.