Best Practices: When to Use StateNotifier vs AsyncNotifier in Riverpod 2.x

[raw-dogging]

Body

Im building a Flutter app with Riverpod 2.x, and I’m a bit confused about when to use StateNotifier versus AsyncNotifier.my state sometimes depends on async operations (like API calls) but also needs to hold sync data that updates based on those results should I just use one type everywhere, or is it better to mix them? How do you structure your state logic to keep it clean and maintainable?

Guidelines

• I have read and understood this category's guidelines before making this post.

[drdixit]

• Use AsyncNotifier for simple data-fetching or one-shot async state.
• Use StateNotifier for more complex or layered state that needs both async and sync control.
• Sometimes even combine them an AsyncNotifier for fetching data, and a StateNotifier for UI interactions based on that data.
  There's no strict rule, its more about keeping your logic clear and maintainable

[raw-dogging]

Thank You @drdixit