From 1afdde1770004a302cd0496f230a349feafa3ee6 Mon Sep 17 00:00:00 2001 From: Brian Rodriguez Date: Mon, 12 Aug 2024 09:25:00 -0500 Subject: [PATCH] Add content to mvp in android (#6474) * Docs(android): Add MVP content * Update src/data/roadmaps/android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md --------- Co-authored-by: Kamran Ahmed --- .../android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/data/roadmaps/android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md b/src/data/roadmaps/android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md index e69de29bb..112957923 100644 --- a/src/data/roadmaps/android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md +++ b/src/data/roadmaps/android/content/mvp@aF_xFIqTjQbENtC7pkXvJ.md @@ -0,0 +1,11 @@ +# MVP or Model View Presenter + +The MVP `Model View Presenter` pattern is a derivative of the well-known MVC `Model View Controller` pattern and is one of the most popular patterns for organizing the presentation layer in Android applications. + +MVP is divided into three components: + +- `Model`: Responsible for managing the data input to the app. This can often be an Interactor or UseCase, handling the business logic and data operations. +- `View`: Takes care of updating the graphical part of the application. It acts as a passive view, only receiving data and requesting actions to be performed. +- `Presenter`: Handles all the logic related to the graphical interface that the View requests. It provides the View with the data it needs to display on the screen. + +This structure helps to create a clear separation of concerns, making your codebase more modular and easier to maintain.