antoniolg/androidmvp

★ 5,905JavaAudience · developerComplexity · 2/5Setup · moderate

Mindmap

mindmap
  root((androidmvp))
    What it does
      MVP pattern demo
      Companion to article
      Code organization example
    MVP Layers
      Model - data layer
      View - display layer
      Presenter - logic layer
    Benefits
      Easier unit testing
      Loosely coupled code
      Clearer separation
    Audience
      Android developers
      Java learners

mindmap root((androidmvp)) What it does MVP pattern demo Companion to article Code organization example MVP Layers Model - data layer View - display layer Presenter - logic layer Benefits Easier unit testing Loosely coupled code Clearer separation Audience Android developers Java learners

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Study how to apply the MVP architecture pattern to structure an Android app in Java with clean separation of concerns.

USE CASE 2

Use as a reference when refactoring an existing Android app to separate display code from business logic.

USE CASE 3

Learn how to make Android code testable by isolating the Presenter layer from the View.

Tech stack

JavaAndroid

Getting it running

Difficulty · moderate Time to first run · 30min

Minimal README, intended to be read alongside the author's external article for full context.

No license information was mentioned in the explanation.

In plain English

"androidmvp" is a sample Android application written in Java that demonstrates the MVP pattern. MVP stands for Model-View-Presenter, a way of organizing code in an Android app so that the logic for what happens (the Presenter) is separated from the logic for what is displayed (the View) and the data layer (the Model). Keeping these three concerns in separate layers makes code easier to test independently and easier to change without breaking unrelated parts of the app. The repository was created specifically to accompany a written article by the author explaining how to apply the MVP pattern in Android development. The README links to that article for the full explanation, meaning the code is intended to be read alongside the article rather than as a standalone reference. Without the article, the repository gives no further description of what the sample app actually does or how to run it. The README itself is minimal and does not describe the app's specific screens, what the sample demonstrates interactively, or how to build and install it. The source code is written in Java, which was the dominant language for Android development before Kotlin became the standard. The project is listed on Android Arsenal, a catalog of open-source Android libraries and samples. Example projects like this one are useful for developers who want to see a specific pattern in action rather than reading abstract descriptions. Because this README is sparse, the value lies in the source code paired with the external article, not in documentation within the repository itself.

Copy-paste prompts

Prompt 1

Based on the androidmvp sample, show me how to create a Presenter class in Java that fetches data and tells a View interface what to display, without the Presenter knowing anything about Android UI classes.

Prompt 2

I'm following the MVP pattern from androidmvp. How do I write a unit test for a Presenter in Java without needing an Android emulator or device?

Prompt 3

Convert this simple Android Activity that mixes UI and data fetching into the MVP pattern used in androidmvp, separate it into Model, View, and Presenter classes.

Prompt 4

In the androidmvp pattern, how should I handle async network calls in the Presenter so the View stays responsive and I can test the logic without mocking threads?

Open on GitHub → Explain another repo

← antoniolg on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.