← Back to all writing
1 min read
Why I Choose BLoC for Large Flutter Apps
A practical look at when BLoC pays off — and when it is overkill.
BLoC gets a reputation for ceremony, and for a five-screen app that criticism is fair. Where it earns its keep is the point where a codebase stops fitting in one person's head.
The real benefit is not testability
Everyone cites testability. In practice the bigger win is where the state lives. With setState, state is wherever the widget happens to be, and a screen that three people edit weekly grows a dozen implicit contracts nobody wrote down.
When to reach for it
- More than one feature reads the same state.
- The team is larger than two people.
- Business rules need to survive a UI rewrite.
If none of those are true, ValueNotifier and a plain service class will get you there with far less code.