Bro... I'm amazed by the effert you put into your tutorial. You show much more then "how to use something", you actually explain the way and the why something is built so. Again, I am amazed by the quality of these tutorials.... Thanks a lot mate.
18 minutes in, Amazing video, One suggestion I would like to give is please don't write everything in one single fine, it gets messy and as you switch pretty fast, It gets confusing as the lines of code crosses 200. All classes, widgets and pages should be implemented and kept outside main.dart
I'm watching your playlist, one by one, getting some knowledge about Flutter and i can say, your video are really great. Quality content, and especially, usefull explaination on every aspect that need attention. I like your mindset about knowing what you do instead of copy / paste code. Keep it up, and thank for the free content.
@Vandad, thanks for your course! Could you please elaborate the fact you mentioned on 50:50, using Provider outside of the build function? As far as I know Provider is strongly tied to context, so we can't use it outside of the build? Or?
Thanks for all your videos! On flutter documentation, the official team refers to provider as "A recommended approach." In your career, what is the state management approach that you use mostly? Or maybe the top 3 that you recommend to know. Do I should learn every one? Thank you very much!!!
why don't you make a series on flutter fire and include all the firebase products from login to RemoteConfig, TestLab. i hope this will help a lot of users
Sir how should i follow your playlists? Should i watch the complete flutter series first and then proceed to dart and state management?? Are there any prerequisites for your flutter series??
@@krishnakumarramachandran5888 Riverpod is nice, but it's a bit behind from Provider and Bloc. Also I have yet to see anyone I know use Riverpod in production. Riverpod is just Proivder without Context. If you know Provider, Riverpod is really easy to learn.
There is no best state management, it depends on your app and which one you are comfortable with. Having said that if you are looking for a job, you must know Provider and Bloc because these scale very well for big apps. Bloc has a lot of boiler plate code but the logic is seperated out very well in it unlike Provider where you can make a complete mess if you don't separate logic and UI from the beginning.
@@marufhassan634 I’m more than confused when it comes to state management in flutter.. I think provider and bloc are way popular but I’m finding it difficult to understand the logic.. silly me 😡
I'm so glad I didn't skip the last 15 minutes because that's exactly what I needed to hear. I was wondering what if I have a bunch of state in different "domains" of my application such as, user authentication, different types of loaded data, ... I don't want that in some kind of super nested "global provider" and I also don't want to have a huge tree of ChangeNotifierProvider. MultiProvider to the rescue!
Nice video! I would recommend adding timestamps and maybe the source code for easier lookups.
Man I'm trying to believe that this content is Free !!!!
Thank you so much.
Big love to your hard work!❤❤
Thank you so much 😀
Thank you Vandad!
My pleasure
Looking forward to the new chapters about riverpod or BLOC.
Both Bloc and Riverpod chapters are out now
Thank you so much! you are a great teacher!
Bro...
I'm amazed by the effert you put into your tutorial. You show much more then "how to use something", you actually explain the way and the why something is built so.
Again, I am amazed by the quality of these tutorials....
Thanks a lot mate.
Thank you very much for dedicating your time to go in so much depth. This is an excellent tutorial!
Good job Sir 💙
can we start this without watching other videos of this playlist.
?
Yes if not otherwise stated during the intro 😊
18 minutes in, Amazing video, One suggestion I would like to give is please don't write everything in one single fine, it gets messy and as you switch pretty fast, It gets confusing as the lines of code crosses 200. All classes, widgets and pages should be implemented and kept outside main.dart
I'm watching your playlist, one by one, getting some knowledge about Flutter and i can say, your video are really great. Quality content, and especially, usefull explaination on every aspect that need attention. I like your mindset about knowing what you do instead of copy / paste code. Keep it up, and thank for the free content.
I'm glad to hear that we think alike. Explaining some aspects of the code sometimes are tiresome but necessary. Thank you
@Vandad, thanks for your course!
Could you please elaborate the fact you mentioned on 50:50, using Provider outside of the build function? As far as I know Provider is strongly tied to context, so we can't use it outside of the build? Or?
As far as I understood. We can use it outside the build function but we need to pass context to that function in which we want to use it.
you can use it but you should pass a context after all watch read and select are just extensions of the context
I'm from Ivory Coast (Côte d'ivoire ) , Thank you so much! your videos are very helpful
Thank you.
You're most welcome
Thank you so much Vandad for such a great course, revisiting it for the second time!
Thanks for all your videos! On flutter documentation, the official team refers to provider as "A recommended approach."
In your career, what is the state management approach that you use mostly? Or maybe the top 3 that you recommend to know.
Do I should learn every one?
Thank you very much!!!
I usually use a combination of RxDart, Riverpod, Bloc and MobX 😊
Can someone help me to understand where we used the overided equality operator?
plz make these videos using android
Thanks
No problem
thanks so much
anyone has the code for this?
thanks this video usefull for me
why don't you make a series on flutter fire and include all the firebase products from login to RemoteConfig, TestLab. i hope this will help a lot of users
Thanks sir
Thanks a lot Vandad for your awesome explanation 😍
My pleasure 😊
Sir plz make a e-commerce type app by using provider
I really like your work, Guruji (teacher)🙏
Awesome videos, is the source available?🙏
U are a flutter shaolin master . Subscribed.
Thank you so much sir it's plusiers !
I wish I could like this more than once
Haha thank you
1:15:00 2nd example
Realy great work
thanks
Thank you 💙
Sir how should i follow your playlists? Should i watch the complete flutter series first and then proceed to dart and state management?? Are there any prerequisites for your flutter series??
If you don't know flutter basics then first watch flutter course then watch state management course
@@krishnakumarramachandran5888 thanks brother
@@abhishekc3556 You are welcome
what a a video full of information.
Glad you liked it 😊
Thanks Vandad for this course. How did you change item to items globally just at one click in 58:53?
How I do this is right click and select rename symbol, and then rename it.
Or just press F2 to rename.
what in your opinion is best among getx bloc and provider? and why? plz reply or provide any useful link on this debate.
Forget getx, it's a bloated piece of garbage. Learn both bloc and provider, they are industry standard. Speaking from experience.
@@madscientist8489 what about riverpod?
@@krishnakumarramachandran5888 Riverpod is nice, but it's a bit behind from Provider and Bloc. Also I have yet to see anyone I know use Riverpod in production. Riverpod is just Proivder without Context. If you know Provider, Riverpod is really easy to learn.
There is no best state management, it depends on your app and which one you are comfortable with. Having said that if you are looking for a job, you must know Provider and Bloc because these scale very well for big apps. Bloc has a lot of boiler plate code but the logic is seperated out very well in it unlike Provider where you can make a complete mess if you don't separate logic and UI from the beginning.
@@marufhassan634 I’m more than confused when it comes to state management in flutter.. I think provider and bloc are way popular but I’m finding it difficult to understand the logic.. silly me 😡
I'm so glad I didn't skip the last 15 minutes because that's exactly what I needed to hear. I was wondering what if I have a bunch of state in different "domains" of my application such as, user authentication, different types of loaded data, ... I don't want that in some kind of super nested "global provider" and I also don't want to have a huge tree of ChangeNotifierProvider. MultiProvider to the rescue!
Glad that you didn't skip the last part. Good to hear your experience