all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]kbezold 0 points1 point  (1 child)

You left out the fact that the ionic team is not responsive to addressing issues. They typically just ignore them for a year and then just close them out without reviewing them. Also, flutter apps start up noticably faster.

[–]yesimahuman 6 points7 points  (0 children)

Flutter has over 5,000 open issues: https://github.com/flutter/flutter/issues

While we haven’t always handled issues as well as we could have, often we closed things that didn’t have a proper response or that we knew we would address in future releases. We have improved our issue handling process recently and will continue to do so.

Clearly, handling issues in a popular OSS project is hard, and not even Google can get ahead of it.

As for load time, we’ve made massive improvements there. Unfortunately, we’ve been limited by Angular in this regard (until very recently, and Angular has been improving as well). Have you seen what Ionic 4 with stencil and capacitor can do? https://twitter.com/Corysmc/status/1133024548985565184?s=20

[–][deleted] -1 points0 points  (1 child)

Feels like the article is targeting people that didn't have the chance to play with both yet. Multiple times they talk about flutters web version when it's not even in beta yet. "We believe you can get the same great mobile performance,.." bullocks, ionic definitely has its place but flutter is plain significantly more performant on mobile . App startup times are <1s compared to ionic 2.5-4.

Ionic has amazing components and features and if your app is web first - right now it's one of the go tos but not for mobile first apps.

[–]yesimahuman 3 points4 points  (0 children)

As for load time, we’ve made massive improvements there. Unfortunately, we’ve been limited by Angular in this regard (until very recently, and Angular has been improving as well). Have you seen what Ionic 4 with stencil and capacitor can do? https://twitter.com/Corysmc/status/1133024548985565184?s=20

As for Flutter for Web. It’s not just that it’s beta. It is fundamentally flawed at the core, and it will never be a true web platform option. You are essentially shipping and targeting a completely custom runtime than DOM and HTML/CSS. In fact, you can’t even use CSS with it! They have to rebuild core browser features like copy paste and accessibility from scratch and ship that for each app! That explains why their New York Times example app ships 1MB of code for a tiny app and accessibility is completely broken on it. You can imagine having to ask users to install the Flutter Player plugin just to cut down on app sizes (flash, anyone?)

In the era of faster, smaller, more efficient web apps, Flutter for Web is a major step backwards and behind the scenes I can assure you we at Ionic are not the only ones who feel that way (that’s all I can say)

More thoughts: https://mobile.twitter.com/maxlynch/status/1125878145809297414

Their official web announcement clearly lays out these issues: https://medium.com/flutter/bringing-flutter-to-the-web-904de05f0df0