Fluttery Framework

A Framework for Flutter's Framework

Allows for faster and easier development with better maintainability. It looks like Flutter because it works like Flutter. There's no 're-inventing of the wheel' here. If you know Flutter, you'll know how to use this.

It supplies the adaptive functions and features expected of a production-ready app:

• An extended State class offering a built-in FutureBuilder or InheritedWidget.
• A State Object Controller class for this State class
• A responsive interface capability from the package, Sizer
• Extensive and essential error handling
• Easy implementation of both the Material & Cupertino interface for one app i.e. One app with both an Android and iOS interface.
• App-wide accessibility to your app's preferences
• A better menu bar
• 27 device event-handlers
• A loading screen option

Fluttery Framework Documentation

• Get started
• StateX class
• State Object Controller
• AppState class
• App's Preferences
• App object
• Error handling
• Testing
• Extensions
• Device Information

Free overview article on medium.com:

Fluttery Framework

As great as Flutter is, you will not create a ‘production-worthy’ app using Flutter right out of the box. When building a Flutter app, it’s expected to be one codebase that runs on an Android phone, an iOS phone, on Windows, on Linux, and or on the Web---and to do so seamlessly. It is to display the appropriate design interface (Material, Cupertino, etc.) depending on the platform it’s running on, it is to have a responsive interface that displays its information correctly no matter the screen size of the device or platform, and it is to fail gracefully if and when it encounters an error. Flutter right out of the box does not have these capabilities. Until now.

When I first started working with Flutter, I began keeping modular bits of code from past projects that generally accelerated the development process. I would use these again and again in future apps---building up a toolkit as we developers often do. Libraries of tried and tested bits of software that I can later put together to reliably supply a particular function or feature. Over time, I turned to the Flutter community for such libraries, and again, if I didn’t find one I liked, I wrote my own:

• Prefs
• State Set
• DBUtils
• l10n Translator
• Remote Config
• StateX

The Fluttery Framework uses packages you will likely need in your own apps. It's a collection of software that's proven to be effective solutions to those capabilities required time and time again by a typical real-world app. It’s an amalgamation of what's great about Flutter and what the Flutter community has contributed over the last years. As the years went by, I found packages that made my life easier and so they too were incorporated into the Fluttery Framework:

• connectivity_plus
• device_info_plus
• flutter_localizations
• go_router (but not before discovering how to fix it)
• http
• package_info_plus
• path_provider
• sizer
• state_extended
• timezone
• universal_io
• universal_platform
• url_launcher
• url_strategy
• uuid

I was careful to choose only packages that fulfill the general requirements of a typical app. After all, this is to serve as a ‘general framework’ for all my apps no matter how diverse each is. Of course, for your specific app with its specific needs, you then will add additional packages or write your own. You supply the specific code; the Fluttery Framework supplies the rest.

Such a framework is to offer a structured approach to making a production-worthy app. For we Flutter developers in particular, a ready means to access a State object’s setState() function is of interest. With that, Fluttery own unique contribution to this package is the concept of a ‘State Object Controller.’ The use of controllers are nothing new to Flutter. It uses controllers in a number of its widgets. It would encourage a separation of an app’s interface from its event handling and business rules promoting a clean architecture. Unlike other options out there, it works with Flutter; not on top of it as a separate approach.