Be easy to replicate when adding new features.Be easy to understand, once the fundamental building blocks are clear.tweaking them to suit the needs of real-world Flutter appsīefore we see what this pattern looks like, let me define some goals.borrowing a lot of ideas from existing patterns.So in this article I introduce a new architectural pattern that I have defined by: However, after building things and taking them apart over and over, I have fine-tuned a technique that works well in all my projects. Over the last year I’ve been building a lot of Flutter apps, big and small.ĭuring this time, I have encountered and solved many problems.Īnd I have learned that there is no silver bullet for state management. My take on state management and app architecture What’s more, making the right choice early on can save us a lot of time and effort. And choosing a technique that will work and scale well as our apps grow is important. Having multiple choices can be a good thing.īut it can also be confusing. Most recently at Google I/O, the Flutter team showed us how to use the Provider package and ChangeNotifier to propagate state changes across widgets.BLoCs are also widely used, and they work well with Streams and RxDart for more complex apps.Scoped Model is known for its simplicity.Truth be told, some state management techniques have proven very popular. And choosing the most appropriate technique depends on what we’re trying to build. This makes sense, because different apps have different requirements. The Flutter team and community have not (yet) settled on a single “go-to” solution. Over the last year, various state management techniques were proposed. State management is a hot topic in Flutter right now.
0 kommentar(er)
