Android MVP Framework

There is a lot of discussion on what would be the ideal way to implement the Model View Presenter on Android . Since there is no "correct" formula, it will be up to you to choose which path to choose. Separating logical interface on Android is an arduous task, but the MVP standard makes it a little easier to prevent our activities from degrading into tightly coupled classes that consist of hundreds or thousands of rows. It is essential to organize the code well in large applications, otherwise it becomes impossible to maintain and extend it.

Here are some articles that will help you understand, so you can better analyze it according to your needs:

• Demystifying MVC and MVP on Android
• MVP for Android (en)
• Introduction to MVP on Android
• Model-View-Presenter: Android guidelines (en)

And these repositories with some details:

• android-architecture
• android-mvp-architecture

See below how it's basically organized:

Accordingtothe android-mvp-architecture in Github, here's a basic application that your architecture would look like:

Asforthe GitHub project , you can see that a lot of people favored it and probably, I say probably, joined. Usually the person to get to the point of using this method, should also have done several other researches and reached a conclusion.

As suggested by @marcio-oliveira , Google itself provides a CodeLab with a brief introduction about the MVP Architecture: Model-View-Presenter (MVP) Architecture .