Android Tutorial 2019 #2: Model View ViewModel Architecture | MVVM PROS AND CONS

Master OOP languages with tutorials from someone who actually cares if you understand how to write beautiful code:

All the above courses are available for 2.99 a month via a youtube subscription to this channel too!

Welcome to part 2 of my 2019 Android Tutorial series. In this video, I explain the funadmentals of the Model View ViewModel Architecture (MVVM), and discuss both the benefits and problems that come from using it. Don't let anyone fool you; there is not a single architecture pattern which works well in all situations. However, MVVM is a great start, and I go in to detail on two variations of the pattern which work better in different situations.

I wrote an article to accompany this video with some more explanation and clear code samples. Consider checking it out:

What is separation of concerns, and why is it important?

Repository link:

Follow the wiseAss Community:

Support wiseAss here:

[pembatamang]

yes! finally. Make it as detailed as possible. I just cannot understand app architecture. I am looking forward to learn it from you.

[bastianf]

Thank you. A very good overview, that gives a lot of answers for question I never were able to search for.

[cyrax]

continue bro I look forward to the next tutorials

[shriharshsaboji]

Can you please start adding all these related videos to in a playlist? It will help in organizing and following the videos easily :) Nevertheless, you're awesome! Keep doing the tutorials :)

[luthiers]

Hello cousin! I have a question, I'm now developing in a company on which my teammates are saying that a ViewModel is analogous to a Presenter, however, I kinda disagree since in my opinion is that a ViewModel is a class that is specified for maintaining a state and a Presenter is a class that should dictate what a specific view should do or look like.... what are your thoughts on that?

[paragkadam]

Great lesson. I am really interested to know how exactly the presenter fits into this MVVM architecture.
I'll let you know my understanding.
The presenter will sit in between the View and the VM, all the UI events will be handled by the presenter and also the display logic will be determined by the presenter itself by observing the LiveData coming from the VM and then convert it into the exact form required to be displayed on the View(The View will no more be observing the LiveData). What this will necessarily do is make the tight coupling between the View and the Presenter but make the VM reusable.
Please correct me if I am missing something.

[rinavall]

Thanks for the detailed explanation, its really helpful. Have you happened to have a video or article about what you use in production code regarding MVVM with Presenter?

[ezscootrr]

Would you recommend a single activity architecture?

[jesuraj]

hi rayn, can u tell which operating system u mostly used for android development ?? linux or windows