Flutter: MobX Crash Course | State Management

Hope you will enjoy the video! You can find the template in the discription, and a bit below that you will see the full project!

Yours video is the only one I found which uses this project, it was very helpful for me as I am just starting with mobx, thanks a lot and please make more project videos using mobx it's a request

hey what is the extension name is those code scratch

What's your opinion about MobX and RxVMS? Do you have a personal preference and why?

Knowing something well doesn't mean that you can teach that as well! As a beginner, there wasn't enough explanation you just copy-paste and a bit words about it and just that!

I am not getting the dispose function from the MobX store

How to show observer values on diffrent screens/class

why is the provider necessary? the observer should be able to be used anywhere without the provider. i thought the whole point of mobx was to not need to create provider trees?

Stop the music in the background, i can't understand what youy're explaining, anyways good video bro

Thanks. Your mobx tutorial is really helpful!

is Mobx have something like Hydrated Bloc to save the current state?

GREAT!

One thing, you use logic inside cart freight, maybe you should be using computed text. But yeah we are still thinking in a Bloc way where business logic and widget logic is separated. We will still need to use logic because of the declarative UI of flutter where we can change UI dynamically based on state properties. MobX will be the most close of MVC we can get. The problem of declarative programming is you will never be able to separate controller from UI 100% .

Nice very nice! thanks

One question: the Observer widget doesn't have any specifics about what it wants to observe. If I have two Observer widgets, related to different fields, I suppose that when I update one field, both Observers will be rebuilt. Is that right? If so, how to avoid unnecessary rebuilds?

Och du har mail! ;)

Have 1 question: What is the importance of Provider with MobX? We can do all operations with MobX. In Which case we need Provider with MobX?

So as you probably said in the conversation with Miklos, you prefer Rx + Bloc over Provider + Mobx.
For a long time, I kept wondering this question as I sought out all over the internet to find the proper answer. But I didn't find any that convincing enough to have me switch to Bloc.
And I was confusing when ppl said Bloc is for a large, complicated app?
I will appreciate you very much if you make a video comparing these two in detail.
What approach you chose and why, and how it is applicable in a complicated app in terms of scalability, maintainability, and performance.
If you chose Rx + Bloc, why Provider + Mobx (maybe + Rx) couldn't help you solve the problem?

Which plugin do you use to display error or info inside the editor? Thanks.

Great video btw

Mobx > provider ?