Managing State in Flutter - Introducing Flutter 

looks like no new videos for this series

Thanks Khanh Nguyen, great content, it's helpful.

thank your latest update after one year:)

One question, can I translate your video into Spanish so that my students can see it on RU-vid to upload it?

Woooo go Khannie!

@@yorjanis5194 Hey, Yorjanis! First, thank you for watching the video and liking it enough to want to translate it for your students :) Second, we actually have Spanish subtitles on this video now! The translations for our videos can sometimes be a bit delayed so it may not have been there yet when you watched the video. Hope this helps your students!

Thank you for being a part of our amazing and energetic community of developers!

GetX better :-)

@@rudinandrey getx is bad in general, not just for state management

@@rudinandrey could you please explain why?

There's even riverpod hooks!

@@marflage easy to use. tools must to be easy. a lot of usefull tools like routing and so on.

I completely agree about BLoC. Awesome pattern and awesome library for flutter.

Yep, plenty to like about flutter_bloc! There's a reason both it and Riverpod are Flutter Favorite packages. :)

They're both really good state management solutions, but Riverpod is definitely very opinionated in how you write models. Provider lets you control things a bit more but with the risk of messier model design.

@@merthyr1831 no doubt, in my opinion Riverpod and Provider have less boilerplate and "etc" package than other state management.

Riverpod is a better "provider". I recommend it.

Hey there! Glad you found the video helpful! Check out the GitHub repository here → goo.gle/3H02gUe. It was hiding under the description's Show More button!

If you're using scoped_model, you must have been coding with Flutter for a while! It's a great package, but definitely one of the oldest approaches to state management.

definitely not.

@@rdrgbaioco What would you recommend? Google itself recommends riverpod.

​@@BrunoCodemanbloc

can you elaborate on how cubits are better for bigger apps?

@@adnanjpg Unlike blocs, cubits don't require boilerplate code. And in reality you will rarely need blocs(only for some complex stream input manipulations) Also you have better control of you state object with cubit/bloc. You can allow your widget tree to rebuild on only specific events. lastly, the business logic code lives on its own files, seperate from UI. You never need to call infrastructure code from UI. testing is a breeze.

@@aytunch nothing special, riverpod has is

Me too realized that only few months ago. Cutely Genius tho.

😅 Forcing us poor lads to watch the previous one?

@@dilshadxahmad no dude, I meant that she's talking about states

@@adolfomotanavarro6553 ok dude, my bad.

It's this video! ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-QlwiL_yLh6E.html "What is State?"

Hey there! What type of content would you like to see for beginners?

what do you mean by you loose encapsulation and OOP concepts? Providers just give access to an object instance

Feel free to provide counter arguments, but I'd argue that's false. You do know what modifies your state: The StateNotifier. Nothing else can modify it..

@@remirousselet6867 It's true that I know by what my state is changed, but I cannot know or force it to be changed form a specific part of the app, obviously if my provider is public I'm able to change its state from any place in the app. Thanks!

​@@talatelbeick6829 Depends. If you're referring to "scoping an object to only one screen", you can do that in Riverpod. It's not true that you can change the state from any place.

@@remirousselet6867 Interesting, how can I be sure that X provider is changed only in deceleration file?

Hey there! I'll make a note to clarify that up front next time so to not be misleading. Just to share my motivation behind this video, I hadn't intended on the video being a full Riverpod tutorial since there's already so much great content from the community which covers it. I wanted to share the concept of state management and RiverPod was a good way to show a more concrete example of the concepts that I discussed, so I glossed over a lot of the implementation details. Plus, we would've needed more than 5 minutes to cover everything ;) Thank you for sharing that feedback, I really appreciate it!

I have the same problem. What changed do need to be made? I'm stuck...

For everyone in the future: 1. Change your TaskItem to extend ConsumerWidget 2. Remove the createState() method from TaskItem 3. Move the build() method from _TaskItemState to TaskItem 4. Delete _TaskItemState, it is not needed anymore. 5. (It not already done, make changes to Checkbox seen in video at 4:44) 6. Change "widget.label" from Text to "task.label" I home this helped someone!