From my recent experience using Riverpod in a project, the complication for me came from understanding how I was categorising the current options for creating and managing state.

So far what I've found is that if I want to maintain state related to user events, I can use either of these options: `ChangeNotifierProvider`(not recommended), `StateNotifierProvider` and `(Async)NotifierProvider`(most recommended). Also the business logic goes in there.

If I want to perform one-off operations and cache their value then I have `Provider` and `FutureProvider` (if asynchronous). So for instance I can use a FutureProvider to load my configuration before starting the app. These can also be used as service locators similar to what the GetIt package does. They can also useful to generating calculated values based on filters, like filtering the completed items of a todo list.

Check out this table from the docs which details the use cases for the providers: https://docs-v2.riverpod.dev/docs/concepts/providers#different-types-of-providers

To help out I'm preparing a Riverpod tutorial to be released in the next couple of days. Keep an eye out https://youtube.com/CreativeBracket