awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
antoniolg avatar

antoniolg/androidmvpArchived

0
View on GitHub↗
5,900 stars·1,553 forks·Java·22 views

Androidmvp

This project is a reference implementation of the Model-View-Presenter architecture for Android applications. It serves as a structural example of how to separate business logic from the user interface through a presenter-based framework.

The implementation focuses on a clean architecture approach, using presenters to mediate all communication between the data model and the view. It employs a passive view pattern and interface-based decoupling to isolate the user interface from domain rules.

The architecture incorporates interactor-based domain logic and layered separation to reduce systemic coupling. This structure enables platform-agnostic unit testing, allowing application logic to be verified within a standard Java virtual machine without requiring the Android framework or a physical device.

Features

  • MVP Implementations - Provides a reference implementation of the Model-View-Presenter pattern to decouple business logic from the UI.
  • Android App Architecture Patterns - Structures the Android application using MVP patterns to ensure maintainability and separation of concerns.
  • Android MVP Frameworks - Serves as a reference implementation of the MVP pattern for building Android applications.
  • Mediator Patterns - Uses presenters as mediators to coordinate the data flow between the model and the display layer.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI
  • Android Implementations - Provides a project structure that separates domain rules and business logic from the Android framework.
  • Interface-Based Decoupling - Uses interface-based decoupling to separate the user interface from underlying business logic.
  • Use Case Interactors - Implements interactor-based domain logic to isolate business rules from the UI layer.
  • Logic-Rendering Decouplers - Isolates view components from domain rules to make the user interface easier to maintain and modify.
  • Logic and Presentation Separation - Isolates user interface elements from domain rules using interfaces for views, presenters, and interactors.
  • Presenter-Based UI Architectures - Implements an architectural design where presenters mediate all communication between the data model and the user interface.
  • Layered Architectures - Organizes the application into distinct model, view, and presenter layers to reduce systemic coupling.
  • Android-Independent - Facilitates the writing of tests for application logic by isolating components from physical devices and the Android platform.
  • JVM-Based Android Testing Patterns - Provides a structural approach to isolating functional components from the Android platform to enable JVM-based unit tests.
  • Platform-Agnostic Unit Tests - Enables logic verification within a standard Java virtual machine by removing Android framework dependencies.
  • Passive View Implementations - Employs a passive view pattern to ensure the view only handles layout and state updates.
  • Component Testing - Verifies application logic by isolating functional components from the underlying platform for unit testing.
  • Star history

    Star history chart for antoniolg/androidmvpStar history chart for antoniolg/androidmvp

    How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

    Frequently asked questions

    What does antoniolg/androidmvp do?

    This project is a reference implementation of the Model-View-Presenter architecture for Android applications. It serves as a structural example of how to separate business logic from the user interface through a presenter-based framework.

    What are the main features of antoniolg/androidmvp?

    The main features of antoniolg/androidmvp are: MVP Implementations, Android App Architecture Patterns, Android MVP Frameworks, Mediator Patterns, Android Implementations, Interface-Based Decoupling, Use Case Interactors, Logic-Rendering Decouplers.

    Which projects share features with antoniolg/androidmvp?

    Projects with overlapping indexed features include: janishar/android-mvp-architecture — This project is a reference implementation of the Model-View-Presenter (MVP) architecture for Android applications. It… sockeqwe/mosby — Mosby is a presentation layer framework for Android applications designed to manage application state and user… git-xuhao/kotlinmvp — KotlinMvp is a short-video Android application developed with Kotlin. It utilizes the Model-View-Presenter… geniusvjr/learningnotes — LearningNotes is a technical knowledge base and engineering study guide focused on Android framework internals, system… tommylemon/android-zblibrary — Android-ZBLibrary is a mobile framework providing core primitives for Android development, including a… jessyancoding/mvparms — MVPArms is an Android application framework based on the Model-View-Presenter pattern. It provides a foundation for…

    Projects sharing features with Androidmvp

    These projects share indexed features with Androidmvp. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
    • janishar/android-mvp-architecturejanishar avatar

      janishar/android-mvp-architecture

      4,425View on GitHub↗

      This project is a reference implementation of the Model-View-Presenter (MVP) architecture for Android applications. It focuses on separating business logic from the user interface by decoupling data logic, UI presentation, and view layers. The implementation distinguishes itself through the inclusion of a boilerplate generator that automatically creates the activity, presenter, and view files required for the MVP pattern. It utilizes a compile-time dependency injection framework to manage object lifetimes and a reactive programming workflow to handle asynchronous data streams and event propag

      Javaandroid-architectureandroid-mvp-architecturedagger
      View on GitHub↗4,425
    • sockeqwe/mosbysockeqwe avatar

      sockeqwe/mosby

      5,439View on GitHub↗

      Mosby is a presentation layer framework for Android applications designed to manage application state and user intents. It functions as an architectural tool that implements both Model-View-Intent (MVI) and Model-View-Presenter (MVP) patterns. The framework utilizes a unidirectional data flow to maintain a single source of truth, ensuring that state updates remain predictable by processing intents through a single logic path. It separates business logic from the view layer to decouple presentation logic from Android Activity and Fragment classes. The system provides capabilities for state ma

      Javaandroidarchitecturejava
      View on GitHub↗5,439
    • git-xuhao/kotlinmvpgit-xuhao avatar

      git-xuhao/KotlinMvp

      3,708View on GitHub↗

      KotlinMvp is a short-video Android application developed with Kotlin. It utilizes the Model-View-Presenter architectural pattern to maintain a clear separation between business logic and the user interface. The project integrates a short-video playback interface that supports content discovery through category filtering and popularity rankings. It employs a Retrofit REST client for network communication and the RxJava reactive framework to manage asynchronous data streams and background tasks. Image loading and caching are handled via the Glide image loader. The application includes capabili

      Kotlineyepetizerkotlinkotlin-android
      View on GitHub↗3,708
    • geniusvjr/learningnotesGeniusVJR avatar

      GeniusVJR/LearningNotes

      13,145View on GitHub↗

      LearningNotes is a technical knowledge base and engineering study guide focused on Android framework internals, system architecture, and mobile performance optimization. It serves as a reference for analyzing the Android boot sequence, process bootstrapping, and system service initialization. The project provides detailed guides on mobile performance, including strategies for reducing memory footprints, identifying memory leaks, and optimizing image decoding. It further covers Android inter-process communication using AIDL and the Binder kernel driver, as well as software architecture manuals

      View on GitHub↗13,145
    Compare all 30 related projects→