Looking at the various patterns to code, you need to find the best practice to be used depending on the use cases. Some of the coding patterns are formed based on the architectural patterns followed by the inherited classes. In those cases, you are restricted to follow one pattern, but there might be instances where you need to make use of certain patterns based on the applicability.
The Model View Presenter pattern is based on the Model View Controller pattern. Since they share several concepts, it can be hard to differentiate between them. The presenter and the controller have a similar role. They are responsible for the communication between the model and the view. That being said, the controller doesn't manage the model and the view as strictly as the presenter does. Separating interfaces from logic in Android is not easy, but the Model-View-Presenter...
