📄️ Navigation
Navigation in Flutter is a complex topic, and it's not directly related to state management.
📄️ Advanced waiting
It's a common task having to show a visual indication that some important process is taking
📄️ Refresh indicators
A refresh indicator is a visual cue to indicate that data is being updated or reloaded.
📄️ Events
In a real Flutter app it's not practical to assume that a Redux store can hold all the
📄️ Waiting for a certain condition
The waitCondition method lets you create futures that
📄️ Selectors
Whether you access your store state with context.state or using a StoreConnector, you will need
📄️ Dependency Injection
While you can always use get_it or any other
📄️ IDE Navigation
In vanilla Redux, actions and reducers are separate objects, and it may not be straightforward
📄️ Persistence
When you instantiate your store, you can optionally pass it a persistor,
📄️ Logging
When you instantiate your store, you can optionally pass it a list of actionObservers and
📄️ Metrics
When you instantiate your store, you can optionally pass it a list of stateObservers,
📄️ Observing rebuilds
Your store optionally accepts a modelObserver, which lets you visualize rebuilds.
📄️ Database and Cloud
How to interact with the database or the cloud?
📄️ Streams and Timers
To deal with Streams and Timers, follow this advice:
📄️ Undo and Redo
It's easy to create undo/redo features in Async Redux. When you create the store, add a
📄️ Business logic
Where to put your business logic?
📄️ Architectural discussion
Reading the following text is not important for the practical use of Async Redux, and is meant only
📄️ Comparisons
Front-end developers learning state management solutions are sometimes