riverpod-offline

To persist Riverpod notifier state offline, configure a local Storage backend like riverpod_sqflite or JsonPersist and call persist inside your Notifier's build method to save and restore state across restarts.

You can use storage backends such as riverpod_sqflite or JsonPersist to save Riverpod state locally, requiring a Storage instance, a unique key, and encode/decode functions to operate.

Yes, Riverpod offline persistence works specifically with Notifier-based providers by intercepting the build method to automatically save and restore state to your configured local storage.

Handle data migrations by defining an optional destroyKey alongside your unique storage key, allowing you to manage data lifecycles and invalidate persisted Flutter state when schema changes occur.

Yes, you can set a cache duration for persisted Riverpod state by configuring optional StorageOptions, which controls state durability and automatically expires stale local storage data.

Test offline state persistence without a physical device by leveraging in-memory storage implementations, allowing you to verify Riverpod state save and restore logic efficiently in tests.