Managing State in Flutter
Course info



Course info



Description
Flutter is arguably one of the best options for creating truly cross-platform mobile applications. One of the challenges that many developers face when learning Flutter, however, is how to successfully apply its reactive data model to real applications. In this course, Managing State in Flutter, you’ll learn about the most commonly used state management options that Flutter offers and when to apply each one. First, you’ll explore how to manage data within a single component using Stateful widgets. Next, you’ll discover your options for sharing state among a collection of widgets using Providers. Finally, you’ll learn how to using the BLoC pattern to separate your application’s business logic from its visual elements. When you’re finished with this course, you’ll have the skills and knowledge of what your state management options are and when to apply them in your own Flutter applications.
Section Introduction Transcripts
Course Overview
Hi everyone, my name is Michael Van Sickle, and welcome to my course, Managing state in Flutter. Flutter is rapidly becoming the first choice for developers that are looking to create truly cross‑platform applications that share a single code base. This course is going to focus in on the tools and techniques that are used to monitor and update application state using Flutter's reactive update model. Some of the major topics that we will cover include managing local state using stateless and stateful widgets, efficiently sharing common state within the widget tree, and how to enforce strong separation of business logic from the user interface with the BLoC pattern. By the end of this course, you'll know the most common patterns for managing application state in Flutter. Before beginning the course, you should be familiar with the Dart language and the basics of creating applications using Flutter. I hope you'll join me on this journey to learn more about this powerful technology with the Managing State in Flutter course, at Pluralsight.