Flutter looks good, but is painful

#1

Post by xhroot » Mon, Aug 05, 2019, 5:35 AM UTC

Flutter looks good, but is painful
medium.com

Re: Flutter looks good, but is painful

#2

Post by latchkey » Mon, Aug 05, 2019, 6:56 AM UTC

I've recently done a bit of Flutter development and have enjoyed it quite a bit. The third party Provider API solves all the state management issues, it should become the default.

OP has some valid points for sure, but fact is that any framework is going to have issues. Just part of the game.

Re: Flutter looks good, but is painful

#3

Post by ibejoeb » Mon, Aug 05, 2019, 7:16 AM UTC

Flutter is young, and there are bugs, but velocity is high and it is advancing the state of the art. It is a huge leap in accessibility and productivity.

I really don't understand the complaint about setup. If expanding an archive and setting an environment variable are that daunting, wait til you try mobile development...

Snark aside, remember phonegap/cordova? Pine for those glory days of low friction?

Re: Flutter looks good, but is painful

#4

Post by TylerE » Mon, Aug 05, 2019, 7:30 AM UTC

Is “one week of electric scooter rental in Bucharest” the new world currency?

Re: Flutter looks good, but is painful

#5

Post by _-___________-_ » Mon, Aug 05, 2019, 7:32 AM UTC

> it took them almost a year to add support for 64 bit in APK

While the author's confusion is understandable, because most of the people posting in the linked Github issue have the same confusion, it's always been possible to build a 64-bit APK (and a 32-bit APK). The linked issue is actually about building a single "fat" APK with both 32-bit and 64-bit native libraries in it, which Google Play Store then repackages to have just the needed library for the device it's being downloaded to.

Shipping two separate APKs has always been possible and gives the same end result for just a little more build process work, which is (/should be) automated anyway.

I've been shipping an app like this for some time now, and it's really not a hardship in any way, certainly not one that justifies the amount of hand-wringing in that Github issue.

Re: Flutter looks good, but is painful

#6

Post by krzat » Mon, Aug 05, 2019, 7:32 AM UTC

I like Flutter very much. In some aspects it is much better than native iOS development. But it's far from perfect, so perhaps this post will prompt Google to hire more people to handle issues.

But, it's not like other companies are much better at this. At React Native they just autoclose them after some time. While Apple most likely has more open issues than Flutter but the data is not public.

Re: Flutter looks good, but is painful

#7

Post by desaiguddu » Mon, Aug 05, 2019, 7:42 AM UTC

I am working on 3 Flutter Applications & 2 of them are currently in production. On average we receive 1 major bottleneck a month, which gets resolved with 3rd Party fixes.

Happy to help if you are stuck on any issue with Flutter. Our background is native application development, so far this is the best Cross-Platform Development toolkit available.

Phonegap, Ionic & others are web wrappers. PLEASE let Flutter grow!

Re: Flutter looks good, but is painful

#8

Post by curyous » Mon, Aug 05, 2019, 7:43 AM UTC

I moved from Flutter to native Android development and found it to be much more pleasant..

Re: Flutter looks good, but is painful

#9

Post by ensiferum » Mon, Aug 05, 2019, 7:47 AM UTC

So.. in summary Flutter is a buggy unfinished and badly designed framework. Nothing new here folks.

Re: Flutter looks good, but is painful

#10

Post by mirceal » Mon, Aug 05, 2019, 7:52 AM UTC

yeah no. i would not bet the farm on this one especially when it comes to developing for Apple devices. Google just doesn’t have the track record to inspire confidence that anything they do is going to stick around