How I Manage Complex State in Flutter with Riverpod StateNotifier

I've been building a Flutter admin panel that handles push notifications, user filtering, audience estimation, and real-time Firestore data. At first I tried setState and Provider, but things got messy fast — especially when multiple screens needed to share and update the same state. Switching to Riverpod with StateNotifier cleaned up everything. Here's how I structure it in production, not just todo app examples. Why StateNotifier over other options? I tried a few approaches before landing on StateNotifier: setState — works for simple screens but becomes a nightmare when you have filters on one screen affecting data on another Provider (vanilla) — better, but ChangeNotifier gets messy with multiple fields. You end up calling notifyListeners() everywhere and losing track of what changed Bloc — honestly felt like overkill for my use case. Too much boilerplate for what I needed Riverpod + StateNotifier — immutable state updates, no BuildContext dependency, easy to test. This clicked for