Book Image

Managing State in Flutter Pragmatically

By : RAHUL AGARWAL, Waleed Arshad
Book Image

Managing State in Flutter Pragmatically

By: RAHUL AGARWAL, Waleed Arshad

Overview of this book

Flutter is a cross-platform user interface (UI) toolkit that enables developers to create beautiful native applications for mobile, desktop, and the web with a single codebase. State management in Flutter is one of the most crucial and complex topics within Flutter, with a wide array of approaches available that can make it easy to get lost due to information overload. Managing State in Flutter Pragmatically is a definitive guide to starting out with Flutter and learning about state management, helping developers with some experience of state management to choose the most appropriate solutions and techniques to use. The book takes a hands-on approach and begins by covering the basics of Flutter state management before exploring how to build and manipulate a shopping cart app using popular approaches such as BLoC/Cubit, Provider, MobX, and Riverpod. Throughout the book, you'll also learn how to adopt approaches from React such as Redux and all its types. By the end of this Flutter book, you'll have gained a holistic view of all the state management approaches in Flutter, and learned which approach is the best solution for managing state in your app development journey.
Table of Contents (14 chapters)
1
Section 1:The Basics of State Management
4
Section 2:Types, Techniques, and Approaches
8
Section 3:Code-Level Implementation

Inherited models – optimizing inherited widgets

If you add print statements in the build methods of MyTextWidget and MyButton, you will notice both getting printed every time the counter is incremented. However, the counter is updated only in MyTextWidget and MyButton has no use of the counter value. Wouldn't it be great if only those widgets which consume the value are rebuilt rather than every widget which is using the .of method? Inherited models to the rescue!

Inherited models are used in place of the inherited widget extension. These models provide the aspect value, which allows the provisioning of rebuilding the selected widgets and not the whole widget tree. Let's update our code a little in order to achieve what we expect.

MyInheritedWidget should now extend InheritedModel<int> instead of an InheritedWidget. As soon as you do that, it will ask you to override a compulsory method named updateShouldNotifyDependent. The overall class should now look...