In one of my earlier tutorials, I have explained why Riverpod is not as good as BLoC or GetX.
Here I will take another approach and explain why Riverpod could be a better choice.
I never really hated Riverpod, but I think it’s difficult to understand. Since there are many concepts, sometimes you get lost in the Providers.
You might not know or remember or understand which Providers to use for your certain need. Since you have to know 8 different Providers. Anyway, I liked technology and started to dig deep into.
My background more about BLoC and GetX. I use them both a lot in work and tutorials.
After learning Riverpod’s provider and how to use them and along with using clean architecture, I have better intuition about it.
After using it a lot I started to feel like, It’s more like GetX. I found Riverpod does one thing very well over BLoC.
It’s Provider to Provider communication. I found Riverpod made it very easy to connect with other Providers and retrieve data as your needs.
BLoC has something called BLoC to BLoC communication. But this is a bit complex mechanism.
Now, I am not going to go into detail about it. Check out here for more detail with examples
