Android MVP vs MVVM and the winner is...

[@codinginflow]

Hell yea, LiveData

[@DanZeevi]

Hell yeah, Florian!

[@arzannebiu7003]

Love this guy. The way he presents and shared the information. 2022 and What we learnt so far, Xamarin is going never to replace iOS & Android Developer :D

[@nishaaggarwal7876]

Great explanation sir! This has cleared my confusion over these two architectures.

[@Chekist2008]

Классная подача материала! Видно, что за плечами есть большой опыт работы со всеми видами моделей.

[@alekseimulin6151]

Great explanation! Even though it's indeed controversial which one is better MVP or MVVM, LiveData, RX or even ThreadPool's, we can argue about it till the end of times and it's all powerful, apart from all of this on the level higher, the explanation of the concept is great!

[@xitize]

Love to listen him, very nicely presented. I agree MVVM is going to be best one for Android developer

[@Kevin509wisdom]

8 months have past, do you still think it's the best architecture for android?

[@soonclass4269]

I really appreaciate the leacture, thank you very much!

[@na-ms1xf]

View 1 * ViewModel. Isn't it View * ---> * ViewModel relationship? Views can bind properties from different ViewModels, whereas those ViewModels may hold references to different Views.

[@holatechm]

awesome explanation sir

[@coder5429]

after the 13 month of this video publish date now Its 25 March 2019 here, let me know what is best for Android Developer now still MVP or MVVM ?

[@cazewonda]

MVVM

[@bayraminanc885]

Mvvm is the answer

[@NyxAndrew]

@@cazewonda nice tip.

[@NyxAndrew]

nice tip.

[@deepakkanyan9241]

awesome explanation

[@igorg.8624]

From a testability perspective, it sounds like MVVM is better than MVP because of its loose coupling...

[@Kevin509wisdom]

Do you have some samples to share?

[@taslimoseni2231]

I love this lecturer!!

[@dawidmat9639]

Great explanation :)

[@hoki8296]

So much fun

[@witoldsienski1709]

Whats with user input events (clicks) in mvvm?

[@harry50650]

View: search_button.setOnClickListener { viewmodel.onSearchButtonClick() } (or via data-binding xml is even better) ViewModel: fun onSearchButtonClick() { //logic }

[@prasannakumar-su7px]

this is awesome

[@erlangparasu6339]

Great!

[@hippiestafarii]

Nice talk :-)

MVP is not legacy code also advise MVVM as a winer is a bad idea, there's no winer.

[@BigCarso]

Presenter doesn't give any actual reasons why mvvm is better. Having a reference to the view isn't bad in itself. Code size is actually more for mvvm. See Google examples and line counts

[@Kevin509wisdom]

"Code size is actually more for mvvm." Code in MVVM is more lines than MVP?

[@BigCarso]

@@Kevin509wisdom yeah a little more, according to the comparison done by Google todo-mvp. I do recommend to use mvvm. Architecture viewmodels provide a lot of benefit

[@KoreanLabx]

howdy?

[@typeblue001]

I did not learn anything from watching this video...