Managing state in Flutter with Provider (Version 3)

[@TheFlutterFactory]

I'll be doing more Flutter videos on state in the future, including Bloc. Are there any issues you had with this video? I'm always looking for ways to improve so leave a comment with any criticisms.

[@aytunch]

I am waiting for the BLOC tutorials impatiently:D They are at version 2 already and it is very stable. I think it is time to do a tutorial on it since it's api has changed dramatically and all the bloc videos out there are nearly obsolete. (I am talking about Felix's flutter_bloc package)

[@TheFlutterFactory]

kzbin.info/www/bejne/rHLCk3WubpeCfpI

[@innovationsapps5601]

It would be great to see a video about GetX, everyone just talks about it now

[@tusharchander8935]

The best video on provider for sure! Thanks!

[@TheFlutterFactory]

Thanks :) I'm excited to do more flutter videos in the future

[@tarkkoprulu7751]

Thank you for your up-to-date provider explanation! This was very helpful and easy to understand.

[@TheFlutterFactory]

Thanks 🙂

[@TirthPatel]

I've recently started using provider package. This video is very helpful for me. Thanks a lot ❤️

[@SunFoxx_]

Thank you a lot, the clearest explanaition, and you are also covered handling of multiple providers. Very helpful

[@purushottampk4530]

This video is good. Helped me a lot. Love from india

[@rahulrvp]

This is super helpful. Thanks for the effort!

[@AamirKhan-zy5yt]

Best explanation. Finally understood the package, Thank You! ❤️

[@chrisogonas]

That was concise, clear and very helpful. Thanks

[@gpiccin]

Really good and simple explanation.

[@senayb3]

wow thanks man this really is starting to make sense

[@shafiulazam3045]

thanks, bro. awesome.

[@monkeygames4467]

Thanks this video is so helpful, keep throwing info

[@blockchainacademy.community]

If you've read the Provider docs and provider counter-example from flutter on Github and you still in some doubt. I highly recommend this video (Y)

[@GK-pu6yp]

Great examples... "but wait people, there is more!"

[@webghost2009]

great, keep doing the best stuff.

[@cvgaviao]

Hi, thank for the video. One question. do we really need a StatefulWidget around the form? wouldn't a Stateless + ChangeNotifierProvider be enough to track the state of a form ?

[@TheFlutterFactory]

The _currentName and _currentColor are only used in this Widget. Therefore, a Stateful Widget is needed. Don't store state outside of a widget if it isn't used in more than one place. You can always refactor later if you need to access those values in more places.

[@dartcode2309]

7:17 setState() is unnecessary. ChangeNotifierProvider will listen for changes in the model object and it will rebuild widget.

[@azharuddinkhan1865]

Right I wanted to say same thing.

[@maheshjamdade1]

agree and if we don't remove setState using provider doesnt make any sense

[@TheFlutterFactory]

Good catch. It was part of the original code and I forgot to remove it. It just causes and additional rebuild. I'm currently working on an update to this video for version 4

[@abdallahhussein5997]

I wish this video can be part two, part 1 could be UI I would like to follow up from scratch

[@ibnukhaldun8625]

thanks this video really help me so much as beginner, compared to bloc, which is better? can we use both in same project?

[@TheFlutterFactory]

Neither is better. It depends on your use case? Provider is a dependency injection library that can be used for state management. Bloc is a state management library. Bloc is better suited towards bigger, enterprise level apps.

[@LUKAS3675]

wow how did I missed the selector feature, thank m8!

[@TheFlutterFactory]

I know. It's great, right? It was only introduced a few weeks ago so most devs haven't tried it out yet. I'll be doing more videos on state management solutions in the future.

[@ilkinhamid1072]

Thank You

[@belqisshida5345]

Widget A. Widget B. Widget C. Here when I update a state in Widget A with provider, the Widgets B and C rebuilds too. So how to avoid unnecessary rebuilds in B and C ?

[@TheFlutterFactory]

That's what consumer and Selector are for. Don't forget the listen flag that I mentioned in the video. That is VERY important if you want access to your provider without listening for changes.

[@AlanTuringWannabe]

I enjoyed your video. Please do a follow up using the FutureBuilder. I'm trying to load in a json file to be used later on in the tree but it isn't rebuilding the children after the future completes. Thank you.

[@TheFlutterFactory]

I'll be doing videos on futures and streams in the near future

[@AlanTuringWannabe]

@@TheFlutterFactory I actually got past my issue. I'll be writing up a Medium entry and posting my code on Github eventually. I'll share my solution when I do.

[@jd31068]

Thanks for this, I just finished Max's course on Udemy (which is very good) the Selector though isn't part of it yet

[@TheFlutterFactory]

Yeah he's great. Selector is very new so I'm not surprised

[@GuilhermeCarvalhoCarneiro]

Hello, first of all congratulations on the content, very interesting. I have a question about the use of the Provider, I am Brazilian and here we have a very active community where in most of the videos it is said that the Provider should not be used in medium and large projects because of the limitation of ChangeNotifier, this information comes ? I wonder why Google would recommend this state manager if it has performance limitations. I apologize for the mistakes, as I do not speak English.

[@TheFlutterFactory]

Because it's a very powerful and useful tool to have in your toolbox. No single tool is useful for all situations 🙂. Bloc is just another good tool. Useful for bigger apps, but overkill for small apps. Many people use both in the same app. Having more than one option is always a good thing

[@GuilhermeCarvalhoCarneiro]

@@TheFlutterFactory I understand, but would it be a mistake to use Provider on large projects, because of its performance or does it actually make no sense?

[@TheFlutterFactory]

Provider is ultimately just a dependency injection solution that can also be used for injecting state. Knowing when it makes sense to use either (or a combination of the two) will come with experience. It's all situational

[@luckie6593]

Is provider + stateless widget a good alternative to using stateful widgets ? Any suggestions ?

[@TheFlutterFactory]

Depends on your situation. There is no one size fits all when comes to software development. If you know for sure you will only have state relevant to one widget (a form might be an example) , maybe you'll just want to put your state locally into a stateful widget.

[@luckie6593]

@@TheFlutterFactory I was thinking the same. Whenever I need a widget with state that is not shared , I will use stateful Widget. Widgets with shared states or data can be stateless with provider

[@Inf0rmatix]

Very good video, thank you so much! Maybe you could cover how you would use Provider with Firebase Collections and Documents? :) Currently working on an app and thinking about the best way to implement some reactive changes to and from firebase. Open to collaboration if you want to, too.

[@TheFlutterFactory]

I just uploaded a video showing how to retrieve data in Flutter. I'm using a ChangeNotifier to store the data from Firestore. There are other ways to do this such as using StreamBuilders, but I will cover real time changes in future videos. kzbin.info/www/bejne/bWSTlol6qrNosMU

[@gaddesathish]

What is the best practice to define ChangeNotifierProvider its app level OR page level?

[@TheFlutterFactory]

What do you mean by 'page level'? The point of using Provider in this video is to provide a reliable source of state across multiple widgets in your app.

[@gaddesathish]

@@TheFlutterFactory Page level means => Single Screen level. I am a little bit confused we need to define providers in screen level or need to define all providers in an app level using MultiProvider and access them in the screen/widget.

[@TheFlutterFactory]

@@gaddesathish Define the providers at the root of your app so they're available to any widgets that need access to them. The official docs provide some great visualizations of the tree structure involved flutter.dev/docs/development/data-and-backend/state-mgmt/simple

[@gaddesathish]

@@TheFlutterFactory Thank you. I got this sentence "You don’t want to place ChangeNotifierProvider higher than necessary (because you don’t want to pollute the scope). But in our case, the only widget that is on top of both MyCart and MyCatalog is MyApp."

[@HP-th3nm]

@@gaddesathish Have you found the answer ? If we define providers in screen level, how we define it? Wrap the 'build' method or wrap when we init that screen ?

[@georgioss1534]

Is this an alternative to Bloc? If so why should I use one over the other?

[@TheFlutterFactory]

Yes. It's a different state management solution. There's also redux, mobx, etc. You should definitely try both. Bloc is purely state management and scales really well. Provider is a lightweight dependency injection solution that also handles state pretty well. It's great for small and medium sized apps. I generally prefer Provider, but you can actually use both in the same app. There's plenty of articles online that do more deep comparisons

[@TheFlutterFactory]

flutter.dev/docs/development/data-and-backend/state-mgmt/options

[@georgioss1534]

@@TheFlutterFactory This is great. Thank you!

[@oluwatobilobaOyelowo]

Link to part 2 of the video...

[@TheFlutterFactory]

There is no part two yet. You can see all the videos on the video tab of the channel

[@insane2539]

@@TheFlutterFactory Please make part 2 on future provider, proxy providers and how to make api calls using providers.