MVP and MVVM

Refer to https://github.com/rajsuvariya/AndroidKotlinStarterProject for the code.

Transcript

1. MVP AND MVVM Raj Suvariya
 Android Developer @Kuliza Technologies
2. WHAT IS MVP?
3. WHAT IS MVP? ➤ Definitely not Minimum Viable Product ➤ Full form of MVP is Model View Presenter. ➤ M - Model (Models representing data) ➤ V - View (Activities, Fragments, Custom Views) ➤ P - Presenter (Mediator) ➤ It’s an structure for writing Android Applications. ➤ It provides separation of concerns, reusability, testability, abstraction of data layer.
4. Source : http://www.androiddevelopersolutions.com/2017/12/android-mvp-for- beginners-android-mvp.html MVP DIAGRAM
5. Source : https://blog.mindorks.com/android-mvp-architecture-extension-with-interactors- and-repositories-bd4b51972339 MVP DIAGRAM
6. LET’S DIVE INTO CODE
7. SO WHAT’S WRONG IN MVP?
8. WHAT’S WRONG IN MVP? ➤ It has 1 to 1 tight coupling with View and Presenter. ➤ It has a lot of boilerplate code. ➤ We need to manually handle device state changes.
9. WHO COMES TO RESCUE?
10. WHO COMES TO RESCUE? ➤ MVVM. (Event driven structure) ➤ M - Model (same as MVP) ➤ V - View (same as MVP) ➤ VM - ViewModel (all the UI logic goes here) Source : https://labs.ribot.co.uk/approaching-android-with-mvvm-8ceec02d5442
11. MVP VS MVVM
12. MVP VS MVVM ➤ Unlike MVP , MVVM doesn’t hold reference to the View. So the tight coupling between View and Presenter is gone. ➤ In MVVM ViewModel provides the data without knowing who is going to consume it. So in MVVM View -> ViewModel relation can be 1:many while MVP has 1:1 relationship. ➤ Less boilerplate code. ➤ ViewModel handles device state automatically :). ➤ Views are easily testable using Expresso, and ViewModel and Models are easily testable using JUnit.
13. ANY QUESTIONS?
14. CHEAP PUBLICITY ➤ Github: http://github.com/ rajsuvariya ➤ Twitter : https://twitter.com/ RAJ_SUVARIYA ➤ Medium : https:// medium.com/@rajsuvariya ➤ E-Mail ID : rajsuvariya@gmail.com ➤ Linkedin: https:// www.linkedin.com/in/ rajsuvariya/