All you should know about Flutter development
1–10 of 101 posts
Re: All you should know about Flutter development
#2A curated list of awesome Flutter libraries, tools, tutorials, articles and more..
Re: All you should know about Flutter development
#3I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.
Re: All you should know about Flutter development
#4I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.
What is the current go to solution for cross platform apps?
Re: All you should know about Flutter development
#5Re: All you should know about Flutter development
#6I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.
I was surprised to see how janky the gallery demo app is on mobile, especially considering Dart is AOT compiled. Apparently Flutter is single threaded too and has a feature called "Isolates" but I'm not sure if they can be used to paint animations off the main thread
Re: All you should know about Flutter development
#7How do the goals of your repo compare to https://github.com/Solido/awesome-flutter?
Re: All you should know about Flutter development
#8I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.
It's always been dart that put me off. For flutter apps supposedly compiling to native code, I don't like using a language that was apparently designed to live within the constraints as a web-based language. There are many other languages that I would rather use instead.
Re: All you should know about Flutter development
#9I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.
It's always been dart that put me off. For flutter apps supposedly compiling to native code, I don't like using a language that was apparently designed to live within the constraints as a web-based language. There are many other languages that I would rather use instead.
I suspect that mid term this is going to be changing. There is currently a big behind the scenes push to move the web target to Wasm (dependent upon Wasm GC landing in some kind of reasonable timeframe).
At that point I suspect you will see the importance of compiling to JS declining rapidly.
Side note: The other major push that seems relevant to some of the other comments here is they are also looking to redo the shader pipeline from scratch and make that AOT compiled as well because right now it tries to just JIT all of that and it isn’t always very predictable as a result. [1]
So combining that along with a WASM target I actually feel super bright about the future of Flutter as a tech choice on web, desktop, mobile etc…
They have some more detail about both of these things in their Roadmap [2] if you’re interested.
Re: All you should know about Flutter development
#10I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app/market but also the skills and experience within your team. No 1 priority is move quickly.
Flutter is brilliant, and probably the way to go, for some apps. A great example of a successful Flutter app is the Sonos app, relatively simple and responsive ui talking to an api. No “rich” or user supplied content. Although they haven’t replaced their desktop app with the flutter app, my guess is that it is the plan.
I think Flutter is brilliant for that type of IOT app, banking/crypto/utilities also the sort that would work well. I don’t think it’s best placed if you want to start using WebViews for some content, when I was last looking at it a year ago there were serious problems.
If you are building a social media app, either Native or React Native (or a combination) is probably the best way to go. You are aiming high so need the best performance and ux.
If you are building a b2b SAAS app I would probably reach for something like Ionic/Capacitor. You can share almost all you codebase with your web/PWA/desktop (electron) apps and can achieve it all with a tiny team. If you need a little more native functionality then adding in NativeScript to a Capacitor works very well.
For an e-commerce app I would probably go Iconic/Capacitor too, the Amazon app for example is mostly webviews.
Productivity apps are much more difficult to recommend for as you probably need large native components.