MVP Pattern

This talk presents a Fundamental of MVP Pattern in Android Devlopement by Moinkhan Pathan

Transcript

2. Android core is it’s self MVC
3. Why not MVC - Everything connected to Everything. - Controller becomes heavy by time - Not Modular - Not Scalable - Not Testable
4. What is MVP exactly?  MVP (Model-View-Presenter) is an evolution of MVC.
5. Separation of Concern  Model & View never communicate with each other.  View layer is completely dumb.  Each layer performs a specific task.
6. Modularity  Packages are not made of components but for screens.  Every screen is in it’s own package containing Activity/Fragment (View), Presenter, Contract.  Easier to modify or add new feature.
7. Scalability  Model layer is given in data repository format.  Model layer is available as Plug & Play.  Modification of layer will not impact another layer.
8. Testable  80% of code resides in Presenter & Model layer.  Easier to write test as everything is broken to modules.  Model & Presenter are pure Java, they can be tested easily using only JUnit.
9. Cons.  Increase the development time.
10. Codelab https://github.com/TechnophileCommunity/MeetupSessions.git