antoniolg/androidmvpArchived
Androidmvp
Este proyecto es una implementación de referencia de la arquitectura Model-View-Presenter para aplicaciones Android. Sirve como un ejemplo estructural de cómo separar la lógica de negocio de la interfaz de usuario a través de un framework basado en presentadores.
La implementación se centra en un enfoque de arquitectura limpia (clean architecture), utilizando presentadores para mediar toda la comunicación entre el modelo de datos y la vista. Emplea un patrón de vista pasiva y desacoplamiento basado en interfaces para aislar la interfaz de usuario de las reglas de dominio.
La arquitectura incorpora lógica de dominio basada en interactores y separación en capas para reducir el acoplamiento sistémico. Esta estructura permite pruebas unitarias agnósticas a la plataforma, permitiendo verificar la lógica de la aplicación dentro de una máquina virtual Java estándar sin requerir el framework de Android o un dispositivo físico.
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.
- 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.
