The use of an architecture pattern is obvious when developing an Android application. For many years, the MVC pattern has been widely used by developers, but today its derived MVP pattern is becoming more popular and important than a predecessor.
Unlike MVC in the MVP pattern we can usually use several Presenters for complex Views. The Presenter is an intermediary between View and Model, and View is separated from Model; also it's easier to create Unit tests in MVP.
Here are four reasons to use MVP architecture:
- In the View item, activity or fragment will be deprived of data processing and just display.
- Ability to test each part separately.
- Independence from the life cycle of the application.
- The Presenter takes a full charge of business logic. There is also an ability to use one presenter by multiple views.
The text above is a summary. You can read the full article here.