Why mvp pattern

Presenter presenter;. Previous Android Architecture Patterns. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Android. Most visited in Java. We use cookies to ensure you have the best browsing experience on our website. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Android.

MVP was one of the famous architecture in Android development few years ago, but more and more people start switching to MVVM pattern now. Too much responsibility in the contract interface, and the interface will keep change according to the view change.

Same as when you want to call something from Presenter to View. As a result, the contract will bigger and bigger from time to time and just looks like a public methods table of your Presenter and View. How can we deal with that gracefully? All business logic, data logic, validate input, receives events from Views, converts data from View to Model or from Model to View is implemented in Presenter. When compared to the View and Controller in the MVC pattern, the View and Presenter present in the MVP pattern are fully decoupled from each other and they communicate by means of an interface.

The Presenter interact with the Views via View interface, it means that the Presenter can perform all presentation and navigation tasks without any dependency on the actual UI technology being used. Our screen has bi-directional-flow , it means that user interactions need to request something from our Model, and the result of this request will affect the View. The View does not interact directly with the Model. This isolates the View implementation bettern than in MVC and allows easier automated unit testing of the Presenter and Model.

The Presenter tends to expand to a huge all-knowing class if we are not careful enough and do not break our code according to Single Responsibility Principle.