Riverpod Tutorial 01 - Understanding the different notifiers 

I'm glad you like the pace of these. Something I tried to focus on in this series

I'm about to watch this. Yay let's go

Thanks😊

South African??

Ohhh yeahhh

😊😊😊

👨‍🏫 thanks

Thanks so much for this comment. Really appreciate it. Will definitely let Remi know about the series at some point. Maybe when it's a couple of videos in

Glad you like it!

BTW, are you still maintaining your patreon? I have not been patreon since I got unemployed. But I would like to join it again :)

Thanks for the interest man. For the time being I'm putting it on hold while I focus on other things :)

Hahaha that's awesome to hear. Sometimes I can't keep the South African in control. I sometimes also drop Afrikaans words by accident.

You're welcome!

Riverpod handles API calls (futures) easily!

Ahh man perfect question. The third video of the series will come out in the next couple of days and will address this. Super excited about the video because it'll have a bunch of great tips to handle this!

Because it’s const, when Flutter rebuilds a part of the widget tree and then it goes down that part of the widget tree it can be certain that the const widgets have already been built and doesn’t need to be again.

Glad you think so! Yeah definitely, will add it to the docs. I've been using Riverpod in production the last two months and have learnt a thing or two. It's still my intention to create a Riverpod series. If you have ideas, or know of struggle areas, please let me know.

Big fan of your content!

@@FunwithFlutter Same here!

Haven't used it😊

At the end of the day use whatever gets the job done. Don't think we should be idealising (or fanboying) any of these frameworks. People are also wired differently. One person may feel more comfortable with GetX and another with Riverpod (to each their own). The "makes your code safer" bit you mentioned is more relevant with regards to Provider -> Riverpod. Not sure if or how this applies to GetX. But Riverpod has compile time safety when it comes to accessing providers. The OG Provider didn't have that and you might often get runtime exceptions saying that you cannot access a particular provider (because the widget you're trying to access it from is in a different part of the widget tree, which is not a problem with Riverpod). You should make a video or blog post on the comparison between Riverpod and GetX. I'd watch/read it. I gave GetX a shot a while back and I was immediately put of when I used the easy routing it provides. The default route transition looked like trash, and that's because it doesn't use the default MaterialRoute transitions (which I expected it to). Sh*t reason to stop using the package as a whole, but that annoyed me and I felt like the package is trying to do too much hand holding and too much at the same time (which may be perfect for a beginner Flutter developer). I know you can opt in to only use the state management that GetX provides, but I like Riverpod :) and it solves the problems I had with Provider. I also like Flutter as is, and don't think it's necessary to create wrapper Widgets for everything I feel Flutter does well on its own. TLDR; Seeing as I went through the effort of typing ALL of this, maybe I am a Riverpod fanboy and you shouldn't listen to me. Use whatever you like to use or whatever gets the job done.

@@FunwithFlutter Thanks for your thoughts.

There's no need for a multiprovider. All the providers are automatically provided

You're very welcome

Thanks for the question. That's only happening because I'm using three separate providers on the three different screens to demo the different ways of creating a counter. The state is being maintained, it's just three separate states. I'm sure somewhere in the video I navigate back to a screen where the count value has already been incremented. If you want to dispose of it then you should take a look at autoDispose on a Provider.

It caused the build method to be called again?

Eventually I want to do an app from scratch

Depends on which ones you're talking about. But I got a lot of the stuff from MotionArray.

One situation for me was when the state was a map of key value pairs. And I wanted to have better control of when to call notifyListeners depending on when the map updated. The map would also update frequently, so it felt like a waste of resources to make the map immutable

@@FunwithFlutter Hmm. I have not tried it. A map is an object a list of key values ​​there should be no problem with the State Notifier. I do everything with StateNotifier but to more easily handling state I use AsyncValue and Freezed or just copyWith().

@@_undecided Same. Can't live without Freezed.

Second one is out! And the third coming soon

I think so! And I'm using it in prod

One of those should give a linter warning. But there are talks to change everything to a more uniform access. So future versions of Riverpod may be a bit easier in this regard

Not sure. I'd need a lot more to go on. But sounds like you're maybe updating the change notifier from a build method. For example calling context.read(provider).doSomething within a build

You can use a Consumer inside your build method to also consume providers.

@@FunwithFlutter Thank u, what about events..such as increment or add .. which modify state, can we do it from stateful widgets

You can if you want to. A StatefulWidget is almost the same as a Stateless widget, it just has an extra state opject. Think of it in a different way, though. See Riverpod as a replacement for handling state through a StatefulWidget. The purpose of a StatefulWidget is to easily manage state in a widget. The purpose of a state management framework (like Riverpod, or Bloc), is to easily manage shared state, that can be used through multiple widget's, not just the single StatefulWidget.