Flutter: State Management with Provider

My personal channels:

[dellaian]

8:52 Keep in mind that in Provider 3.0.0 (the latest) the "notifier" have been changed to "value", eg: CounterBloc())

[SamuelGuebo]

Definitely the best guide I've watched so far on Flutter's Provider. It's well explained and straight to the point. Thanks Paul!

[mohammedyousif]

The best video I have ever seen on flutter State management using Provider package. Thanks a lot.

[georgeruellan]

I had to watch this twice but I've got my head around it now. Thank you!

[PurvikRana]

Simply the best to understand what is provider and how it's working in flutter.

[kolya]

I always like random people who teach like this. Straight forward explanation and examples,

[paulbaker]

Thank you for the short article. However - I would just like to point out :


a. This has nothing to do with BLOC. What you have shown is basically MVVM. I would be inclined to therefore rename your components and drop the BLOC annotations as this may become confusing to dev's who are just starting Flutter and believe they have now learnt Bloc. Bloc is reactive and Stream-based. Provider is simply inherited widget on steroids.


b. For simple applications - using a provider at the root of the app is okay. For more complex apps with very large widget trees - I would not recommend adding every single provider at the root of your app, both for performance & manageability reasons. Additionally as of v3 of provider, ProxyProvider was introduced which may lead to lots of proxyprovider stringing when we try and inject into objects within the widget tree that do not contain a build context. Thus, in my experience, it is best to not provide a global Provider at the root of the app but to instead inject Provider on a per-case basis, use sparingly where it is needed, remember Provider.of(context) in your Build() methods is not a cheap operation - especially if your widget tree is very large. FWIW my apps are reactive, I use RxDart and Bloc throughout and a hand rolled Provider<T> class..

[fernando_her]

Amazing tutorial, thank you! Keep this videos coming Paul!, you got a new subscriber

[emafriedrich]

Excellent tutorial. The main principles is explained for a rapid understanding of the pattern.

[Sameer_Kumar]

hey paul, saved my day. Best explanations are often simple and yours is one of them. keep it up.

[neozes]

Very well written and recorded explanation. Good job! You should definitely pursue this path.

[HezOmanjo]

Nice & simple explanation. Thanks Paul!

[rikyriky]

Wow this is simply the best video of state management in Flutter. I can now clearly understand the concept of Provider.

A tiny question: is it a good approach to wrap the whole app with the multiprovider and insert providers into provider=[ ] as you did in the video?

Of course, this way I can simply call any bloc from anywhere of the app since it’s all covered. Also I can add new blocs to the list and they will also be available immediately for the whole app.

Does that have a disadvantage?

[michaelangelomagat]

Yes thank you for this bro. Because I am a RN dev but I want to switch to flutter world and finding the best state management nice one

[mustofa_id]

1:05 flutter create flutter_bloc && cd $_

Underscore variable save last param of your last command.

Btw, great explanation.
Thank you!

[uzaird]

Thanks a lot Paul! Have been following you since Ionic 3 times.

[stefanciobotaru]

thanks, keep up the good work. You explain very well

[xD]

Clean, on point and straight up to the code !
Well done mate .
+1 sub .

[animatrix]

The article link points to a "Not found" webpage, does this mean you've pulled it out cause it's not up to date or something ?

[brijeshgw]

well explained, easy to understand. do you have video of implementing bloc for login state management?