The ‘Little More’ Series
A Little More Framework for the Flutter Framework makes for better apps
Little more Adaptive
Little more Life Cycle Handling
Little more Error Handling
Little more Control
Little more Efficient
Little more App
Little more Ability
I’ve always said, as great as Flutter is, you will not create a ‘production-worthy’ app using Flutter right out of the box. Of course, making such a statement is not without some pushback:
“I don’t understand why I should use and learn some Fluttery Framework, when I already use and know Flutter.” — reddit.com/r/FlutterDev
“I would definitely say you can build a production-ready app right out of the box, it all depends on the feature requirements.” — reddit.com/r/FlutterDev
Prove It
That was about a year ago, and I’m still steadfast in my position. I began the [**Fluttery Framework**] package back in 2018 supplying the typical functions and features needed for a production-worthy app. It certainly made my Life easier when building apps as it became a culmination of what Flutter already offered as well as sound Dart packages from the Flutter community.
Each article in this series will have a title suggesting what I felt the ‘right out of the box’ Flutter needed a ‘little more’ of to produce apps ready for release. In most cases, it was simply a matter of implementing the very classes and core packages already found in Flutter.
It’s a Choice Not a Chore
My motto has always been ‘Keep It Flutter’ when writing Fluttery. It works with Flutter; not on top of it as a separate approach. It doesn’t impose itself on you. It works with Flutter because it works like Flutter — it looks like Flutter. If you know Flutter, you’ll know Fluttery.
I needed a framework to quicken the building of Flutter apps; to enhance the building process resulting in a reliable and robust end product. However, as Dave Farley suggests, one that wouldn’t impede my code but fulfill the needs of each unique project. Have I done it? You be the judge.
Cheers.
