Suggesting third-party approaches (Bloc, Redux, Mobx, etc.) is never the objective of this book. The core objective of this book is to write your code with the core and standard approaches that are native to Flutter and will help maintain your code in the long run, rather than increasing your dependency on third-party written code and packages that are not guaranteed to be updated, can be outdated or discontinued as soon as the writer runs out of resources or has no time for it or has some personal reasons not to update. Standard approaches described in this book stay with Flutter core libraries. Flutter core libraries are written by Google engineers with rigorous testing and will be part of Flutter in the long run. In the future, you will only make no or very less changes to keep your projects up to date with Flutter's latest version once you carefully write your code with these approaches. This book covers the following concepts.Why we need an ArchitectureFlutter states insightsPassing states and widget-rebuildingState RestorationCreating state objects using ChangeNotifierPassing state objects down the widget tree using InheritedWidgetPassing states down the widget tree using Provider a simple Inherited widget wrapper libraryscoped_model a complete state management solution, extracted from the Fuchsia codebaseSee Architectures being used in real-world projects Reply APP and Shrine AppSee real-world code samples written by Google developers and othersA must-have course to learn how to write code with a good architectureAfter studying this book samples you will be in the top 1% of programmers who can write code with a good architecture