Well, my experience is different. The main complexity is in the business logic, the overhead that BLoC brings is not that big for medium and big projects.

Also, I think that Riverpod (same as Provider) solves a different task – it is about providing the state, while BLoC is about implementing your business logic. As I've mentioned in the article, BLoC (especially with bloc library) is mainly a State Machine pattern under the hood, and this is aligned with my vision on how to architect a mobile app.

If you're using BLoC just to provide one state, this really seems excessive for me, and I wouldn't recommend using BLoC for that.

I have some arguments against Riverpod, but we're successfully using both Provider and BLoC within one app, as I've mentioned, they're solving different tasks.