It would be nice if you wrote out your conclusion instead of providing an image that I can't even see as it opens so small. And "Source" links to your homepage? This is useless!

On a high level BLoC and Provider do the exact same thing: they are state management libraries. Doesn't matter how you spin the terms and code, what they do is maintain state of your application and your widgets can listen to changes in that state.

Provider doesn't outright say it's for business logic, but you can use it exactly as BLoC. Just inject your repository there and that's it.

However, I myself am very much against having your business logic inside a Flutter application, mobile application or any front-end application at that. Typically, a mobile application is simply your presentation layer ie. it communicates with an API and that's where your business logic should be. Behind that API. If you start sprinkling your business logic everywhere, maintenance will be a pain.

Of course if your mobile app doesn't connect anywhere and it simply works with a local database, then that's fine. You need to have that business logic inside the app. But in case it's just a front for an API, then no.