Simplicity at its best... Someone give this guy a 🏅🏅🏅🏅 I've struggled with state management for a while and other UA-camrs are just downright confusing. Thanks man really. You've just earn yourself a subscribe
some timestamps i have on my notebook: 00:00-5:05 - basics 5:05- 24:00- example using setstate 24:00 - same example using provider 35:00- (listen: false) concept 44:14- context.watch and context.read concept 51:00 - about consumer hope this helps!!
Have gone through so many provider tutorials for the past 5 days. Haven't come across anything like your tutorial. The best explanation from my point of view. Worth an hour! you have done a great job. Thank you so much ;) Kindly upload many videos in future.
You sir,, are the best teacher under the sun. you could have shown us all this in 8 mins but u took yo time to explain everything in depth with no complicated terms. hat off for you.
Verbose, repetitive, ‘excessive’ detail … EXACTLY what I needed to begin to understand Provider. Good for beginners and (IMHO) even better for us intermediate Flutter ‘wanabes’. Ten years teaching experience in a major public university shows me that this good teaching! 👍
Dude, sorry for my bad english I'm a iOS developer, and trying to learn flutter :D And your video tech me me a LOT. It's the best video that I saw about provider It's short, simple, well explained and with a lot of examples
listen.. LISTEN!! i have been struggling with Provider for weeks because i didnt understand how it gets passed and configured.. after watching your video.. i have a blackbelt on Provider.. i can pass anything from screen to screen without hassle.. you have no idea how thankful i am for this video. you sir earned a like and a sub.
The basics as well as the fundamentals are very important in order to really learn something, and this guy is doing a great job! Keep on uploading simple and amazing tutorial videos like this one!
Your tutorials are great. they are well explained, i feel like I'm in the school again. some channels just show some codes but they don't help us to learn. thank you for being different and keep it up.
Thank you very much for this video! It really helps me understand basic use of Provider and how state management works. You also took the extra miles to explain us about efficiency in the last part of the video. Cheers!
This tutorial was AMAZING. Thank you so much for explaining with simple code. I just tested an implemention of this on a same app and it works beautifully. Thank you again!
Hats off. I was a bit confused with the topic but Now I feel satisfied. Subscribed and also shared the video with all my students and friends. Thank you, Man. God Bless you!
Beautiful explanation my man, you have explained why to use it and what are the benfits of the same... this is how one must explain with a practical example. Thnx a lot and have a great day! Subscribed ❤ Something I have just tried and observed rn is that instead of using 'Consumer' we could also just extract the widget into a new Statless widget, so basically we're rebuilding only this build method of our new Statless widget which is then reflected in all the places where we create this Stateless widget instance(more like we're changing the scope of the widget to be rebuilt to only the one that's actually listening to the state property change). Example : class Screen4 extends StatelessWidget { const Screen4({Key? key}) : super(key: key); @override Widget build(BuildContext context) { print('Building Screen4'); return Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ TextWidget(), //A listener. ElevatedButton( onPressed: () { //context.read is same as Provider.of.. listen is set to 'false'. context.read().changeData("Ronaldo"); }, child: Text("Change data"), ), Screen5(), ], ), ); } } class TextWidget extends StatelessWidget { @override Widget build(BuildContext context) { print("Building textwidget"); return Text(context.watch().name); } } Please let me know if there's any performance issues with this method, thanks!
Hi, sorry, I do not have time to test. Test it out and use print statements like I did in my video. You will pick up unnecessary builds that way. Also look at using Selector instead of Consumer to only watch a certain set of values.
@@JohanJurrius Yes sir, I did try it and it works the same way as consumer(basically both does the same thing that is they wrap the widget with a builder method so that only the nearest build method is rebuilt). And I have also used selector and it's amazing, just as you said we can listen to a specific value of our provider type. By the way you videos have taught me a lot, not just how it works but how I can test it myself to predict the behaviour as I code, and that's what made the difference for me. Thanks a lot brother! Love from India ♥
Coming from a React background you showed exactly what I imagined setState state management would look like with (passing on the callback through props). I went with Provider immediately since it looks fine for my purpose. I am however curious what the difference in terms of use cases is with Bloc. As far as I've gathered is that with Bloc you less locked into Flutter and that it's more reactive(?) so it might scale better?
thak you very much ..... but i have just one question in the first example we could just creat an instance of the screen one on the screen Four than we could acces directy without passing from the other screens and with that we could also updat the data with a setstate
I followed this tutorial and facing a problem. When the app restarted the value resets to default. I tried to use Shared preferences to save the previous state, but failed. Can you please explain how to do that?
The John Rambo reference alone already deserves a thumbs up. Great videos.
Simplicity at its best... Someone give this guy a 🏅🏅🏅🏅
I've struggled with state management for a while and other UA-camrs are just downright confusing.
Thanks man really. You've just earn yourself a subscribe
some timestamps i have on my notebook:
00:00-5:05 - basics
5:05- 24:00- example using setstate
24:00 - same example using provider
35:00- (listen: false) concept
44:14- context.watch and context.read concept
51:00 - about consumer
hope this helps!!
supper thanks bro
easy explanation
please make a video on adding to Wishlist
Have gone through so many provider tutorials for the past 5 days. Haven't come across anything like your tutorial. The best explanation from my point of view. Worth an hour! you have done a great job. Thank you so much ;) Kindly upload many videos in future.
Thanks beyond Thank you,
You explained a concept I've been having trouble with for a long time. Thank you very much!
You sir,, are the best teacher under the sun.
you could have shown us all this in 8 mins but u took yo time to explain everything in depth with no complicated terms.
hat off for you.
you debunked "curse of knowledge" ...bravo!! this is how you make a tutorial
Fantastic explanation! Very simple and easy-to-follow example, perfect and paused diction. Thank you very much, sir!
Long but clear video. Thanks
Verbose, repetitive, ‘excessive’ detail … EXACTLY what I needed to begin to understand Provider. Good for beginners and (IMHO) even better for us intermediate Flutter ‘wanabes’. Ten years teaching experience in a major public university shows me that this good teaching! 👍
Thanks, appreciate your comment.
The best explanation for Provider. Thank you so much.
You're skills to explain are top class! Best explanation I heard so far
Dude, sorry for my bad english
I'm a iOS developer, and trying to learn flutter :D
And your video tech me me a LOT. It's the best video that I saw about provider
It's short, simple, well explained and with a lot of examples
fantastic explanation!!!!
listen.. LISTEN!! i have been struggling with Provider for weeks because i didnt understand how it gets passed and configured.. after watching your video.. i have a blackbelt on Provider.. i can pass anything from screen to screen without hassle.. you have no idea how thankful i am for this video. you sir earned a like and a sub.
The basics as well as the fundamentals are very important in order to really learn something, and this guy is doing a great job! Keep on uploading simple and amazing tutorial videos like this one!
Undoubtedly the best introductory video.
This is one of the best explanations for Provider! 🙌
great explanation!
Your tutorials are great. they are well explained, i feel like I'm in the school again. some channels just show some codes but they don't help us to learn. thank you for being different and keep it up.
Thank you very much for this video! It really helps me understand basic use of Provider and how state management works. You also took the extra miles to explain us about efficiency in the last part of the video. Cheers!
very simple explanation. understood provide along with callback which was confusing for me. Thank you....
Thanks for clear explanation !🙂
This tutorial was AMAZING. Thank you so much for explaining with simple code. I just tested an implemention of this on a same app and it works beautifully. Thank you again!
really good video..thanks for the upload
Excellent tutorial! You have a gift man. Cheers!
Hats off. I was a bit confused with the topic but Now I feel satisfied. Subscribed and also shared the video with all my students and friends.
Thank you, Man. God Bless you!
Super helpful, well explained too Dankie!
what an amazing explanation!!Thumbs up..Thank you very much.
Excelent explanation, very well!!!
Beautiful explanation my man, you have explained why to use it and what are the benfits of the same... this is how one must explain with a practical example.
Thnx a lot and have a great day!
Subscribed ❤
Something I have just tried and observed rn is that instead of using 'Consumer' we could also just extract the widget into a new Statless widget, so basically we're rebuilding only this build method of our new Statless widget which is then reflected in all the places where we create this Stateless widget instance(more like we're changing the scope of the widget to be rebuilt to only the one that's actually listening to the state property change).
Example :
class Screen4 extends StatelessWidget {
const Screen4({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
print('Building Screen4');
return Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
TextWidget(), //A listener.
ElevatedButton(
onPressed: () {
//context.read is same as Provider.of.. listen is set to 'false'.
context.read().changeData("Ronaldo");
},
child: Text("Change data"),
),
Screen5(),
],
),
);
}
}
class TextWidget extends StatelessWidget {
@override
Widget build(BuildContext context) {
print("Building textwidget");
return Text(context.watch().name);
}
}
Please let me know if there's any performance issues with this method, thanks!
Hi, sorry, I do not have time to test. Test it out and use print statements like I did in my video. You will pick up unnecessary builds that way. Also look at using Selector instead of Consumer to only watch a certain set of values.
@@JohanJurrius Yes sir, I did try it and it works the same way as consumer(basically both does the same thing that is they wrap the widget with a builder method so that only the nearest build method is rebuilt).
And I have also used selector and it's amazing, just as you said we can listen to a specific value of our provider type.
By the way you videos have taught me a lot, not just how it works but how I can test it myself to predict the behaviour as I code, and that's what made the difference for me.
Thanks a lot brother!
Love from India ♥
Thanks for the reply. Thats how you learn. Appreciate the reply and info.
Excellent
Again... an excellent explanation....loved it...
best explanation
Well explained ❤
Awesome explaining 👍
Super explanation 👍
Great explanation, thx !
thank you so much
God bless you Johan :)
Keep going buddy!!!
Coming from a React background you showed exactly what I imagined setState state management would look like with (passing on the callback through props). I went with Provider immediately since it looks fine for my purpose.
I am however curious what the difference in terms of use cases is with Bloc. As far as I've gathered is that with Bloc you less locked into Flutter and that it's more reactive(?) so it might scale better?
thak you very much ..... but i have just one question in the first example we could just creat an instance of the screen one on the screen Four than we could acces directy without passing from the other screens and with that we could also updat the data with a setstate
super... Thank you
Please upload video on block (using plugin)state management
hey! you should do riverpod
best
How is the elevatedbutton not part of the widget tree but the text widget is?
Amazing tutorial, could you share your source code please?)
I followed this tutorial and facing a problem. When the app restarted the value resets to default. I tried to use Shared preferences to save the previous state, but failed. Can you please explain how to do that?
Yes, in this example we do not save the state. You can check my SharedPreferences video on how to do that: ua-cam.com/video/v821-8FO4MU/v-deo.html
@@JohanJurrius Thank you for the reply. I found it in your channel after commenting. Just finished it. thank you
Listen true will make the repository to get data every second from server...
Is that true? Why not you try about riverpod dude?
you kind of over explained main.dart in this video and wasted lot of time
Dear sir/madam. Just a reminder that this is for beginners. You indicated earlier you are advanced. Maybe this playlist is then not for you.
@@JohanJurrius :)
@@JohanJurrius having this posted on GitHub for reference will help a lot too :)
Thanks so much