Working with the navigation example at Flutter.io I felt there must be a better way to work this issue … and a little searching found this article:
Came across a nice article: http://bizz84.github.io/2018/03/18/How-Fast-Is-Flutter.html discussing Flutter performance (its a few months old) vs a similar timing app in iOS. It’s main takeaways are (confirming suspicions): Frequent UI redraws are expensive If you call setState() often, make sure that it redraws as little UI as possible.
Flutter seems like the antithesis of MVC (Model-View-Controller) development approach but one person has come up with (I expect a computationally intensive) approach discussed at: https://proandroiddev.com/flutter-in-mvc-437ed7cead2e.
Nice example at github of a pubspec.yaml that has everything. Published 8/15/2018
Nice (but small) non-technical write-up on how Flutter and Fuchsia (an in-the-works Google’ one-OS-for-all) may have significant business impact in 2019. Wikipedia offers a good summary of the state of Fuchsia here: https://en.wikipedia.org/wiki/Google_Fuchsia. They summarize the link to Flutter and Dart as: Fuchsia’s user interface and apps are written with
Out at medium there is a nice article that discusses the different approached to “screen painting” of the UI using traditional Andriod and now Flutter. Here is the top of the article: What even are Flutter widgets? Flutter is a mobile UI framework that makes UI
Flutter via Material Design has access to a hundreds of monochrome icons. Check them out here: https://docs.flutter.io/flutter/material/Icons-class.html
Video and code covering most of the basic constructs. He starts with a blank editor and build up examples line by line so you really get a feel for the widget tree and how state is created and maintained. The only issue is that the
A company called AppTree had a nice talk at Dart Con 2018 about their successful efforts creating a Android/iOS/Web solution that had 70% common code.
Getting a good handle on the Flutter Widget Tree seems like a key to avoiding “flutterstration” since the widget cascade can store key values and constrains well above the widget that holds the actual context.