-
Notifications
You must be signed in to change notification settings - Fork 0
Home
- Foreword
- What Is the Purpose of this Guide?
- Who Is this Guide For?
- Topics that Will Be Covered
- Creation Context
- How Was this Guide Written?
- What Sources Were Used to Create this Guide?
I want to use this foreword to give credits to Sebastian Faust [1] and DevonFw [2] for their excellent Flutter guide [3]. The guide is well written, and its structure has been a massive inspiration for my guide.
The goal of this guide is to set an entry point for state management in Flutter.
I want to help Flutter developers and Flutter development teams that have to decide which state management solution (SMS) to choose for their app to determine which SMS is most likely the right tool for the job.
It should provide a reference about which state management solution is likely the right one to choose to build an example, small-scale, middle-scale, or large-scale application.
Or at least show the advantages and disadvantages of each solution so that you can make an educated decision yourself.
This guide is for Flutter developers and Flutter development teams that are planning their next Flutter project.
It is for people who are overwhelmed by the amount of state management solutions provided by the community. For people who are searching for information about which SMS is in line with their requirements and why they should think about choosing it.
The topics that will be covered are:
- some prerequisites that you will need to understand how Flutter works under the hood to realize state changes in the UI.
- the methodology behind the guide
- the results of the methodology, represented by the implementation of each SMS
- an evaluation of the implemented SMS based on specified criteria
- a recommendation on which SMS is suited for example, small-scale, middle-scale, and large-scale applications
- a conclusion of my personal retrospective view on the guide and its future as well as my future work
For the Bachelor’s degree in the Bachelor of Science Program, “Business Informatics” at Technical University Cologne [4] the students have to deliver a project which includes some of the practices taught in the study program. Furthermore, they have to write documentation along with the project. This guide is my version of the documentation.
This guide is written for developers. Therefore, I want to keep it informal - from developer to developers. Throughout the guide, I will use the pronoun “you” to keep it that way.
To get a full understanding of the guide, I advise to read it from chapter 1 to chapter 5. If you are only interested in the recommendations, jump straight to chapter 4, section 3 - Recommendations.
Most of the code examples, explicitly the code snippets in chapter 3 - Results, are taken from SME-APP, which is the example application that has been build for this guide. The full source code for the app is found here.
To highlight definitions, you will find the following approach throughout the guide:
| 📕 | Term | Definition |
|---|
For the creation of this guide, a collection of books, blog posts, journal articles, official documentation, and YouTube videos has been used. In chapter 6 - References, a list of all sources used in this guide can be found.