Skip to main content


I've been experimenting with Riverpod a lot the last couple weeks and am now ready to try it in a greenfield project I've been meaning to write for some time. In lieu of a good design patterns/best practices book (if one exists I haven't found it anyway) I've been doing as best homework I can with finding videos/blog posts and little side experiments. One thing I discovered earlier this week was nested providers which I was thinking I may want to use to replace another idiom I had been using of having a provider that takes an item ID. Based on this presentation by @Randal Schwartz :vv: :vv: it sounds like that is not the way to go. In the video he does show how to do various scoping, both literal scope and logical scope, of providers in Riverpod. #riverpod #flutter #DartLang
in reply to Hank G ☑️

After trying lots of state management libraries, I finally settled on watch_it. I really like it:

https://pub.dev/packages/watch_it

in reply to Clifton Labrum

Interestingly I have been using a combination of GetIt and Provider 2.0 in my current main app project: getIt for DI and composition for things not part of the widget tree, and Provider for the rest. Riverpod letting me do all that in one system with change notification propagation throughout was the big draw.
in reply to Hank G ☑️

I tried Riverpod a couple times and just couldn’t wrap my head around it. WatchIt feels simple to me (like Provider) but with the goodness of GetIt built in.

It’s nice that we have so many options!

in reply to Clifton Labrum

When I first started Flutter and couldn't get my head wrapped around state management Riverpod was the new hotness and I just couldn't get there. I did get my head wrapped around Provider. When I wrote this post series to show how flexible Dart and Flutter were for deployment targets I had no choice but to use something other than Provider since there were non-Flutter implementations. I decided to give Riverpod a second try and really liked it.

I was just saying yesterday that Flutter's agnosticism on things like state management is a double edged sword. It drastically increases the learning curve for less than trivial apps but it's nice having the flexibility once you get used to it. #flutter #DartLang