MVP in android (Model View Presenter)

Model-View-Presenter pattern fit s for android 

• serving as an entry point
• rendering the  components
• routing user events to the presenter

This allows us to implement our model like :

View - this contains UI components, and handles events for them.

Presenter - this will handle communication between model and view, it as a gateway to the model. Meaning, if we have a complex domain model representing, god know what, and our view only needs a very small subset of this model, the presenters job is to query the model and then update the view.

Model - this should basically be full domain model, hopefully it will help making your domain model more "tight" as well, since we wont need special methods to deal with cases

MVP separates the UI concerns between the data of the UI (Model), the display of the UI (View), and the logic of the UI (Presenter). For Android, the View is the Activity, which will handle gathering user input and updating the display; the Presenter is a class that will handle communication between the Model and View; the Model will handle persisting and retrieving data, along with any business logic that the data must adhere to. Interfaces will be used to de-couple each of these components