Yes, I have been using Riverpod for quite some time now. Riverpod makes my life so much easier. Previously I used Provider for most of my projects but certain limitations made me switch and Riverpod was the No Brainer for me since its very similar to Provider and is superior . I would highly recommend you to give it a try if you're looking for a state management solution.
Cool I will check it out for sure! I'm sticking with provider for now for most projects and have not found many limitations yet. Can I ask you which were the limitations you encountered? And what were the reasons you chose Riverpod over other solutions, like let's say, redux or mobx?
I'm also doing research on these topics, so it would be really interesting to hear about that too!
The first and far most important thing about Riverpod is that it helps in keeping the business logic and the Widgets separate making the Widget Tree clean and easier to read.
The second thing is that Provider is not compile-time safe.For instance, Provider will only prompt you with an error at runtime If you try to use a Provider that does not even exist.
Another one is the if there are multiple providers of same type within the widget tree, Using Provider, you can only listen to the one which is closer to the Consumer Widget. With Riverpod, you can consume any provider anytime and even anywhere since the Providers are globally defined.
And the list goes on.I hope it helped! If you need more help with it, let me know!
Yes, I have been using Riverpod for quite some time now. Riverpod makes my life so much easier. Previously I used Provider for most of my projects but certain limitations made me switch and Riverpod was the No Brainer for me since its very similar to Provider and is superior . I would highly recommend you to give it a try if you're looking for a state management solution.
Cool I will check it out for sure! I'm sticking with provider for now for most projects and have not found many limitations yet. Can I ask you which were the limitations you encountered? And what were the reasons you chose Riverpod over other solutions, like let's say, redux or mobx?
I'm also doing research on these topics, so it would be really interesting to hear about that too!
The first and far most important thing about Riverpod is that it helps in keeping the business logic and the Widgets separate making the Widget Tree clean and easier to read.
The second thing is that Provider is not compile-time safe.For instance, Provider will only prompt you with an error at runtime If you try to use a Provider that does not even exist.
Another one is the if there are multiple providers of same type within the widget tree, Using Provider, you can only listen to the one which is closer to the Consumer Widget. With Riverpod, you can consume any provider anytime and even anywhere since the Providers are globally defined.
And the list goes on.I hope it helped! If you need more help with it, let me know!
Makes sense, thanks for the info. I might get in touch once I start researching more about it!
I'm here if you need help. Just let me know