The first thing to clarify is that MVP is not an architecture by itself, it’s only responsible for the presentation layer. Ideally, the MVP pattern would achieve that the same logic might have completely different and interchangeable views. The MVP pattern allows separating the presentation layer from the logic so that everything about how the UI works is agnostic from how we represent it on screen. There have been breaking changes about architectural patterns since then, such as MVVM with architecture components, but MVP is still valid and an option to take into account. So I’ve decided to update it solving most of the doubts people had, and also convert the code to Kotlin. This article was first published in April 2014, and been the most popular since then. MVP (Model View Presenter) pattern is a derivative from the well known MVC (Model View Controller), and one of the most popular patterns to organize the presentation layer in Android Applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |