Flutter state management without the tears
Provider, BLoC, Riverpod… The choice matters less than you think. Start simple, understand why, and move up only when it hurts.

State management is the topic that scares new Flutter developers most. Search for it and you will find a dozen packages, each with passionate fans and long arguments about why the others are wrong. It is enough to make anyone freeze.
It shouldn't. State management is just an answer to one question: where does this piece of data live, and who is allowed to change it? Once you see it that way, the choice of package becomes much less dramatic.
Start with setState
For data that belongs to a single widget, the built-in setState is perfectly fine. A counter, a toggle, the text in one form field: keep it local and keep it simple.
class _LikeButtonState extends State<LikeButton> { bool liked = false; @override Widget build(BuildContext context) { return IconButton( icon: Icon(liked ? Icons.favorite : Icons.favorite_border), onPressed: () => setState(() => liked = !liked), ); }}Move up when data is shared
The moment two screens need the same data, such as the signed-in user or a shopping cart, passing it through constructors becomes painful. That pain is the signal to reach for a shared solution, not before.
Choose a tool when you feel the problem it solves, not when a tutorial tells you to.
Then pick one tool and learn it well
- Provider is a great default for small and medium apps, and easy to read.
- BLoC suits teams that want strict structure and clear events.
- Whatever your future team already uses is the best choice of all.
The concepts transfer. Someone who truly understands Provider will pick up BLoC in a week, because the hard part is deciding where state lives, not the syntax.
How we teach it
In the Mobile path, trainees build their app with setState first and deliberately run into the pain of shared data. Then we introduce Provider and refactor together. For the final project, we show the same feature written with BLoC, so they have seen both styles before their first job.
The goal is not to crown a winner. It is to make sure that, faced with a new codebase, our graduates can read any of them calmly.






