Flutter Provider - State Management using PROVIDER ( A BLoC Alternative)

ChangeNotifierProvider<DownloadFile>(
builder:<=this builder has been deprecated in newer version
//for latest versions go with this one
create: (context) =>DownloadFile(),
child: instaInterface(),

),

At last a fantastic explanation on actual use of state management rather than showing pics of streams and rivers moving boats. Question - i am starting app thats “simple” but foresee could get more “complicated” features, can provider handle it or start now with bloc. Dont want to rewrite the codes later. Which state management is recommended by google?

Great introduction to Provider. Read a lotabout it but this is concise and clear. One thing, I had to replace "builder" with "create" in:
...... return ChangeNotifierProvider(
create: (context) => WeatherInfo(),
child: Scaffold( ...

Best man

make some tutorial about Overlay please

Nicely explained the concept man much appreciated!

Awesome tutorial about Providers! Quite nice to manage states! Thank you so much! Keep it up!

what will hapen if there is another class called Stockinfo along with weather info? how to use builder in this case?

It's better if we make public variable for this dynamic variable inplace of this big complycated circle

Provider is not a state management solution as said by Remi in his video
It only seeks to provide values deep inside the widget tree

In a job interview ... (Almost nailed it but then)
Recruiter: So, we use BLOC for all of our projects. You are familiar with it, right?
Me: GG. Um out.
(Just for fun no offense btw)

Thank you for a really solid video!

Again nice video od my type and need this a lot

what if i have multiple weatherinfo objects, how do you differentiate inside of the consuming widget? how do you declare multiple notifier objects?

do i have to use bloc if i use provider? (newbie question)

which one of these 2 approaches (property based vs consumer based) has better performance? Will property based approach leads to whole stateless widget be re-constructed when notification arrives?

Thanks dude!! I 've finally understood provider, cheers

Perfect example and a good explanation, keep rocking!

You explained this so nicely, thanks dude, appreciate it.

My provider is working fine on debug mode. But when I released the app to stores, the changes are not working. Do you know something? I will use bloc

I am a complete newbie with Flutter, been reading about state management and for the life of me I could not get it...until I saw your video...thank you very very much for this...

Mine didn’t work until I used the setState method to change the TemperatureType unlike you did in yours, is there a reason for that?

Well explained. Thanks a lot

Please explain in a way every one could get it the way you have explained only some extra smart students had got your point I couldn't get anything

great video！！！！ Activate Windows。。。。。。。hahha！

Bro the tutorial was great. But can I get the code on github so that I refer it whenever needed?

A great video explaining the very basics of the Provider Pattern. I was confused which to choose from Bloc and Provider, now I have my answer. Superb <3

This might be a silly question or I might have an old fashioned mindset, but lets suppose we have a list of items. we want to listen to the state of that list. So when the user adds a new item, we`ll be notified. But here comes my problem in understanding: i want to handle the state of each new, per user generated, item (which is just a new instance of a class). Do I need to have a new (kind of dynamic) provider for each of the items? How can I accomplish that, or is that approach not even necessary? Thanks in advance. Chris

Nice Teaching. Thanks for sharing

this video is gold, thanks

Thanks, nice tutorial

What vscode extension used to display the lines for the indentation guide?

is this code available on github?

Thanks

Awesome 👍

Can you PLEASE EXPLAIN FIRST THEN RUN.


The Basics:
1) DO NOT BOTHER to RUN EXAMPLE half way of explaining the code unless you already explain everything you have written.
2) Unless you STARTS WITH EXAMPLE and THEN explain the CODE.

Do not do your work as teacher half way, explain code (half-way), run example, then continue explain code (where you left), it is annoying, seriously.

This is great and pretty easy to comprehend. One thing i'm not sure though, how would you access a provider from inside another provider? Example, how would you call another provider from the inside of WeatherInfo class where you don't have access to the context?

it was very useful thanks man :) i was confused with the provider it really helps to understand better. Do you have the same kind of video for bloc and redux and what is the pros and cons then it will blast.

Very well done

BIG THANKS @RetroPortalStudio
Before watching this video I was kind of tensed and irritated with this utter confusing state management stuff.
It literally had wasted my 2 days.
I have become your fan. Hope you have more on flutter. I'd explore your channel regularly now on.

So, the Provider its like a Singleton ? We have this instance that we will manipulate in diferents widgets of the application, and as we manipulate this instance it will reflects in all other parts of the app(that use this object), because its the same instance, i get it right?

how to avoid unnecessary rebuilds? example:


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 ?

that photoshop way of describing is very nice idea, thank you!

Will you be able to post the code to github?

Awesome video !! We need more videos on PROVIDER! Like the architecture and other useful functions!

what's the difference between with keyword and extend keyword ?

EXCELLENT Tutorial !!!