Android Architecture MVP Pattern
10 likes3,868 views
The document discusses the Model-View-Presenter (MVP) architecture pattern, emphasizing the separation of responsibilities among model, view, and presenter components. It highlights the importance of following the single responsibility principle and demonstrates a login MVP implementation using a GitHub repository. The goal is to allow for interchangeable models and views without mutual dependency.
Android Architecture MVP Pattern
- 2. MOTIVATION • Activities with millions of callbacks. God objects. • Single Responsibility Principle • https://github.com/antoniolg/androidmvp • http://en.wikipedia.org/wiki/ Single_responsibility_principle
- 3. MVP RESPONSIBILITIES • The model defines the data to be displayed or acted upon. • The view is a passive interface that displays data and routes user events. • The presenter retrieves data from the model, and notifies the view to display it.
- 6. MVP ModelPresenterView User Events Update Model State Changed Event
- 7. MVP ModelPresenterView User Events Update Model UpdateViews State Changed Event
- 12. LET’STRY IT! $ git clone git@github.com:jpotts18/android-mvp.git
- 13. GOAL • Demonstrate MVP • Switch out Model without affecting theView • Switch out theView without affecting the Model