Package selection guidance compiled from public package information, community data, and project usage.
HydratedTriple is a Flutter/Dart package that simplifies state management by automatically persisting and restoring store state across app restarts. Built on top of the Triple pattern, it integrates seamlessly with Riverpod or Provider, enabling developers to maintain user data like preferences, login status, or form inputs without manual serialization. The mixin handles saving state to local storage (e.g., SharedPreferences) and rehydrating it when the app launches, reducing boilerplate and improving user experience. It’s ideal for apps requiring reliable state persistence with minimal setup.
Use cases
Persisting user preferences
Restoring login state after restart
Saving form data temporarily
Maintaining app settings across sessions
Handling offline-first scenarios
Key features
Automatic state persistence
Seamless integration with Riverpod/Provider
Supports multiple platforms
Minimal boilerplate
Built-in serialization
Cross-platform compatibility
Suitable for
Apps needing persistent state
Developers using Triple pattern
Projects with offline functionality
Teams prioritizing developer productivity
State management with minimal code
Considerations
Requires proper serialization of state objects
May increase app startup time slightly
Not suitable for large or frequently changing state
Limited to simple state structures unless custom logic added
Depends on underlying state management solution
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Triple - Segmented State Pattern
Welcome to Triple!
Design Pattern for State Management.
Triple is a nickname to SSP (Segmented State Standard).
Some packages were created to make it easier for developers to start using the standard. We'll call it an extension.
Segmented State Pattern (SSP)
When we talk about a single flow state, we end up solving architecture problems early, as we will have only one data flow for each state.
In addition to the maintainability and to the ease of use architecture, we also have the possibility of increasing this flow with other standards such as the Observer, which gives reactivity to the component when it is modified, and Memento, which makes it possible to revert or redo this state.
A beautiful example of a pattern with a single flow is BLoC, giving reactivity to a state allowing all transformations in that flow. This (although complicated for some), consolidates very well in the architecture of a project, even the limits of this practice are beneficial for not allowing the developer to resort to other solutions for the architecture and the standard for its resource.
There are other ways to promote reactivity in a property instead of the entire object, such as MobX's Observable and Flutter's ValueNotifier, and that gives us a lot of choices. However, we lose some important architecture limits, which can put in check the project maintenance in the future. Therefore, it needs a standard to force limits on the individual reactivity of each property and thereby improve the maintainability of the components responsible for managing the states of the application.
Triple is a nickname to SSP (Segmented State Standard). Some packages were created to make it easier for developers to start using the standard. We'll call it an extension.
This project is distributed under the MIT License. See LICENSE.txt for more information.
✨ Usage
The SSP segments the state into 3 reactive parts, the state value (state), the error object (error), and the state loading action (loading).
These segments are observed in a listener or separate listeners. They can also be combined to obtain a new segment, always starting from the 3 main segments.
Installation
Dependencies
add the following dependencies to your pubspec.yaml file:
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the appropriate tag.
Don't forget to give the project a star! Thanks again!
Fork the Project
Create your Feature Branch (git checkout -b feature/AmazingFeature)
Commit your Changes (git commit -m 'Add some AmazingFeature')
Push to the Branch (git push origin feature/AmazingFeature)