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!
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