Thanks for the overview. I wonder if it is possible to recommend a state management package for a specific use case like a Flutter UI with a network client underneath that sends commands to a server and then react depending on the server responses, i.e. changes the UI. From the overview looks like BLOC is a good fit, but maybe I am wrong? What would you recommend?
Hi Lovin, a lot of users of Flutter love getX and would recommend it. I personally be very careful with it. In my opinion a it is a anti pattern to have a package that tries to solve every problem. It is not only state management it is also routing, DI and more. It can be a great help to get something up and running, but if you search for long time solutions in a larger project I would not recommend it because the maintenance price tag could become quite large.
Thanks for your feedback :). Is it possible, I am pretty sure, and there is already a package that does exactly this. There is even a package that tries to achieve exactly that. pub.dev/packages/bloc_redux But I am not sure if it is a good idea, behind each package there are a big fanbase and community, and most likely there is a reason why they decided for one pattern or the other. Another way would be to work with RxDart and create your own "bloc" pattern like, for example, GroovinChip and Luke Pighetti explained in their interviews.
I kept waiting for GetX. Besides, this state management package is more used and famous than all the others mentioned, except for Provider. Hopefully you'll talk about it later. Anyways. Thank you for making this video and again, nice Job! Sharing this vid.
Hi thanks for letting me know, I have getX on my todos, but I am a bit negativly biased and want to try to get more information and maybe talk with some experts before I announce my oppinion to it :). I am happy that you liked the session so far.
In the context of State Management of Flutter, Can we say like State Class used to return the state object that contains Stateful Widget? [Especially when the createState() method called.]
Uf, that is a tough one. I gutess you could say that. The only problem is that there is more than just a Stateful Widget that could contain state, also Services that are used inside of your widgets could contain state. But as a general rule of thumb I guess this is pretty accurate!
Hi Toasticuss, for me, it started the first time I required three different ChangeNotifier at one point and, I needed to wrap three Consumers around each other. That lead to a tremendous sized widget. It could be that it was just wrongly used, but other packages helped me there a lot. I think that Provider is a right choice and will work, but in large-scale projects, I would not rely solely on it. Maybe more boilerplate was wrongly chosen, and it should be more confusing or bloated widget tree.
@@FlutterExplained You can use MultiProvider in order to make the code look cleaner. pub.dev/documentation/provider/latest/provider/MultiProvider-class.html
@@FlutterExplained I think it depends on the situation. I'm trying to learn Flutter myself at the moment, so unfortunately I don't know if I do this right but I wrap each widget separately with Consumer if it needs to be notified about changes.
@@mivoligo That sounds right :) the problem is just that if you have a widget that needs multiple consumers, then the widget tree gets bit messy but I will show in my video what I mean :). Thanks for sharing your conserns.
Yes of course in 8:44 I talked about it. It is great in most cases and in smaller apps. You could only run into long-term issues with boilerplating and other packages have additional features that help but the trade off is higher. I hope that helps.
I'm learning state management for the first time at moment. I loved the video as an overview of the current solutions. I can't wait for the provider video. I think it's the best one to start with for beginners. Note: maybe it's my phone speaker, but the audio can be improved. It's slightly not enjoyable to listen to.
Great question! Not really, a global variable could contain state as for example Riverpod does. But Not all global variables are state. It is the state you want the program to be in if the global variable contains the background color, then yes it is your state of the background color. If you use the global variable only to contain information that you need for a calculation then no it is not really the state. I hope that helps.
![Lp. Сердце Вселенной #30 ДВА В ОДНОМ [Один человек]• Майнкрафт](http://i.ytimg.com/vi/nrXy15orKhY/mqdefault.jpg)
Max, thanks for the high level introduction to state management and the clean use of diagrams to support your descriptions!
You are most welcome Paul, thank you for your amazing feedback :)
Thanks for the video. Now I have a clear idea to start with State management
That's a top quality video. You definitely deserve a lot more views and subscribers.
Thank you, I am glad that you think so :)
Thanks for your explanation, it is clear enough.
Thanks for the overview. I wonder if it is possible to recommend a state management package for a specific use case like a Flutter UI with a network client underneath that sends commands to a server and then react depending on the server responses, i.e. changes the UI. From the overview looks like BLOC is a good fit, but maybe I am wrong? What would you recommend?
I like your videos buddy. You crushing it!
Thank you so much!
Awesome content, keep up the good work.
Thank you, I give my best :)
Hi , I came across getx package for state management.
What do you think about this package?
Hi Lovin, a lot of users of Flutter love getX and would recommend it. I personally be very careful with it. In my opinion a it is a anti pattern to have a package that tries to solve every problem. It is not only state management it is also routing, DI and more.
It can be a great help to get something up and running, but if you search for long time solutions in a larger project I would not recommend it because the maintenance price tag could become quite large.
it would have been better, if you have shown any code. anyhow good video, thank you.
There are multiple follow up videos for different state management libs like setState / provider and redux :) feel free to check them out.
I really loved the video. Is it possible to use redux in combination with bloc? and is it a good idea to do it?
Thanks for your feedback :). Is it possible, I am pretty sure, and there is already a package that does exactly this. There is even a package that tries to achieve exactly that. pub.dev/packages/bloc_redux
But I am not sure if it is a good idea, behind each package there are a big fanbase and community, and most likely there is a reason why they decided for one pattern or the other. Another way would be to work with RxDart and create your own "bloc" pattern like, for example, GroovinChip and Luke Pighetti explained in their interviews.
Nice video mate!
Thank you, I am glad that it helped you :)
I kept waiting for GetX. Besides, this state management package is more used and famous than all the others mentioned, except for Provider. Hopefully you'll talk about it later. Anyways. Thank you for making this video and again, nice Job! Sharing this vid.
Hi thanks for letting me know, I have getX on my todos, but I am a bit negativly biased and want to try to get more information and maybe talk with some experts before I announce my oppinion to it :). I am happy that you liked the session so far.
@@FlutterExplained Thanks! It seems to me that you are proceeding professionally, and I like that. Hoping to watch that video! And again, keep it up!
Very good video, thank you!
You are very welcome, I am glad that you enjoyed it!
In the context of State Management of Flutter, Can we say like State Class used to return the state object that contains Stateful Widget? [Especially when the createState() method called.]
Uf, that is a tough one. I gutess you could say that. The only problem is that there is more than just a Stateful Widget that could contain state, also Services that are used inside of your widgets could contain state. But as a general rule of thumb I guess this is pretty accurate!
Does stateless is like functional component in react?
Correct, dumb and without any state :)
What are examples of too much boiler plate code with the provider package? It seems to have the least amount.
Hi Toasticuss, for me, it started the first time I required three different ChangeNotifier at one point and, I needed to wrap three Consumers around each other. That lead to a tremendous sized widget. It could be that it was just wrongly used, but other packages helped me there a lot. I think that Provider is a right choice and will work, but in large-scale projects, I would not rely solely on it. Maybe more boilerplate was wrongly chosen, and it should be more confusing or bloated widget tree.
@@FlutterExplained You can use MultiProvider in order to make the code look cleaner. pub.dev/documentation/provider/latest/provider/MultiProvider-class.html
But this helps only with the registration not with the consumer right?
@@FlutterExplained I think it depends on the situation. I'm trying to learn Flutter myself at the moment, so unfortunately I don't know if I do this right but I wrap each widget separately with Consumer if it needs to be notified about changes.
@@mivoligo That sounds right :) the problem is just that if you have a widget that needs multiple consumers, then the widget tree gets bit messy but I will show in my video what I mean :). Thanks for sharing your conserns.
What about Provider? Is it good enough?
Yes of course in 8:44 I talked about it. It is great in most cases and in smaller apps. You could only run into long-term issues with boilerplating and other packages have additional features that help but the trade off is higher. I hope that helps.
I'm learning state management for the first time at moment. I loved the video as an overview of the current solutions. I can't wait for the provider video. I think it's the best one to start with for beginners.
Note: maybe it's my phone speaker, but the audio can be improved. It's slightly not enjoyable to listen to.
Thanks for the note I will check and look if I can improve it for the next time :)
Is it like global variables in a way?
Great question! Not really, a global variable could contain state as for example Riverpod does. But Not all global variables are state. It is the state you want the program to be in if the global variable contains the background color, then yes it is your state of the background color. If you use the global variable only to contain information that you need for a calculation then no it is not really the state. I hope that helps.
12:10 Best State Management solution is here. :-)
Wow this video is recorded on the 2. June :O how much has changed since then is absolutly incredible.
@@FlutterExplained 😀. Whenever I get doubts I usually look for "MyFlutterDoubts flutter explained" 😂🤣
👍👍
SUBED
Welcome to the family :)
GetX?
1. Explanation of individual methods were very shallow.
2. Introduction wasnt concise. Over explained introduction.
Very low signal to noise ratio.
Thank you for your feedback, we will try to improve that in the future.
@@FlutterExplained💙