text
stringlengths
1
372
general overview
things to review before selecting an approach.
<topic_end>
<topic_start>
provider
<topic_end>
<topic_start>
riverpod
riverpod works in a similar fashion to provider.
it offers compile safety and testing without depending on the flutter SDK.
<topic_end>
<topic_start>
setState
the low-level approach to use for widget-specific, ephemeral state.
<topic_end>
<topic_start>
InheritedWidget & InheritedModel
the low-level approach used to communicate between ancestors and children
in the widget tree. this is what provider and many other approaches
use under the hood.
the following instructor-led video workshop covers how to
use InheritedWidget:
other useful docs include:
<topic_end>
<topic_start>
june
a lightweight and modern state management library that focuses on providing
a pattern similar to flutter’s built-in state management.
<topic_end>
<topic_start>
redux
a state container approach familiar to many web developers.
<topic_end>
<topic_start>
Fish-Redux
fish redux is an assembled flutter application framework
based on redux state management.
it is suitable for building medium and large applications.
<topic_end>
<topic_start>
BLoC / rx
a family of stream/observable based patterns.
<topic_end>
<topic_start>
GetIt
a service locator based state management approach that
doesn’t need a BuildContext.
info note
to learn more, watch this short package of the week video on the GetIt package:
<topic_end>
<topic_start>
MobX
a popular library based on observables and reactions.
<topic_end>
<topic_start>
flutter commands
reactive state management that uses the command pattern
and is based on ValueNotifiers. best in combination with
GetIt, but can be used with provider or other
locators too.
<topic_end>
<topic_start>
binder
a state management package that uses InheritedWidget
at its core. inspired in part by recoil.
this package promotes the separation of concerns.
<topic_end>
<topic_start>
GetX
a simplified reactive state management solution.
<topic_end>
<topic_start>
states_rebuilder
an approach that combines state management with a
dependency injection solution and an integrated router.
for more information, see the following info:
<topic_end>
<topic_start>
triple pattern (segmented state pattern)
triple is a pattern for state management that uses streams or ValueNotifier.
this mechanism (nicknamed triple because the stream always uses three
values: error, loading, and state), is based on the
segmented state pattern.
for more information, refer to the following resources:
<topic_end>
<topic_start>
solidart
a simple but powerful state management solution inspired by SolidJS.
<topic_end>
<topic_start>
flutter_reactive_value
the flutter_reactive_value library might offer the least complex solution for state
management in flutter. it might help flutter newcomers add reactivity to their UI,
without the complexity of the mechanisms described before.
the flutter_reactive_value library defines the reactiveValue(BuildContext)
extension method on ValueNotifier. this extension allows a widget to
fetch the current value of the ValueNotifier and
subscribe the widget to changes in the value of the ValueNotifier.
if the value of the ValueNotifier changes, widget rebuilds.
<topic_end>