MVP Pattern for Android

Model-View-Presenter Pattern used in Android application development makes developing easier.

Transcript

1. Model-View-Presenter(MVP) Pattern for Android Raka Westu Mogandhi Brownbag Onebit Friday July 31th
2. What is MVP? Software design pattern on Android that separates presentation layer from logic.
3. MVP vs MVC • MVP Pattern – View is more loosely coupled to the model. The presenter is responsible for binding the model to the view. – Easier to unit test because interaction with the view is through an interface – Usually view to presenter map one to one. Complex views may have multi presenters. • MVC Pattern – Controller are based on behaviors and can be shared across views – Can be responsible for determining which view to display
4. MVP Structure
5. Why use MVP? • Makes view separated from data source → code is easier to scale and maintain. • Makes testing approach easier.
6. Examples • https://github.com/onebithq/MvpTemplate • https://bitbucket.org/onebit/wobe-mvp
7. Future Implementation • RxJava/RxAndroid usage to manage data flow. (Example: https://github.com/zsiegel/rx-mvp-android) • Separate model layer using UseCase/Interactor-Repository Pattern – Repository → Get data from data source (network, database, etc.). – UseCase/Interactor → Get data that will be used on presenter from repository. •