android10/Android-CleanArchitecture-Kotlin
Android CleanArchitecture Kotlin
Este proyecto es una plantilla de aplicación Android de referencia en Kotlin y un conjunto de implementaciones de muestra que demuestran los principios de Clean Architecture. Proporciona un diseño estructural que aísla las reglas de negocio centrales de la interfaz de usuario y las fuentes de datos en módulos distintos y en capas.
La implementación se centra en el patrón Model-View-ViewModel (MVVM) para desacoplar la lógica de UI de los modelos de datos. Utiliza un framework de inyección de dependencias para automatizar la creación de objetos y gestionar los ciclos de vida de los componentes, mientras emplea un patrón de repositorio para abstraer las solicitudes de datos a través de fuentes de memoria, disco y nube.
La arquitectura incorpora una organización de paquetes basada en características y configuraciones de compilación modulares para mantener la consistencia en todo el proyecto. También incluye una estrategia de pruebas integral que combina pruebas unitarias para la lógica de negocio con instrumentación para la UI y módulos de simulación (mock) para la validación de la capa de datos.
Features
- Android App Architecture Patterns - Demonstrates structural design patterns and Clean Architecture principles for building maintainable Android applications.
- Kotlin Android Starter Kits - Provides a comprehensive Kotlin Android starter kit demonstrating Clean Architecture principles.
- Data Source Routing - Provides a repository implementation that routes data requests between memory, disk, or cloud sources based on availability.
- Android App Modularization - Employs strategies for decoupling the application into independent feature modules to optimize structure and build consistency.
- Repository Pattern Abstractions - Implements the repository pattern to abstract data access and decouple the domain from specific persistence details.
- Clean Architecture Frameworks - Utilizes a clean architecture framework to enforce the separation of business logic from infrastructure.
- Feature-Based Code Organizations - Organizes source code by functional feature domains into dedicated directories to improve cohesion in multi-module projects.
- Multi-Module Architectures - Employs a multi-module architecture that separates the application into presentation, domain, and data layers.
- Dependency Injection - Demonstrates techniques for decoupling software components using a dependency injection framework.
- Constructor-Based Injections - Employs constructor-based injection to provide required collaborators and improve the testability of components.
- Logic and Presentation Separation - Separates business logic and data fetching from visual components to keep the UI independent.
- MVVM Patterns - Implements the Model-View-ViewModel pattern to separate business logic from the user interface.
- Use Case Orchestrators - Provides dedicated use-case orchestrators to coordinate interactions between external interfaces and domain entities.
- Model-View-ViewModel - Implements the Model-View-ViewModel pattern to keep the presentation layer independent of the underlying business logic.
- Business Logic Isolation - Isolates core business rules into a pure module independent of the user interface and external frameworks.
- Domain Workflow Orchestration - Provides an abstraction layer that coordinates domain services and data retrieval to fulfill specific business use cases.
- Build Logic Centralizations - Centralizes build configurations and dependency versions within dedicated directories to ensure consistency across modules.
- Result - Uses sum types via sealed classes to encode operation outcomes as distinct success or failure variants.
- Dependency Scopes - Constrains the lifetime of injected objects using scopes such as application-wide or activity-specific lifecycles.
- Asynchronous Control Flow - Implements patterns for managing asynchronous operations to ensure the user interface remains responsive during business logic execution.
- Asynchronous Error Handling - Provides patterns for managing and propagating errors occurring within asynchronous data flows.
- Background Thread Dispatchers - Utilizes background thread dispatchers to isolate heavy processing tasks from the main UI thread.
- Dependency Injection Frameworks - Integrates a dependency injection framework to manage component lifecycles and facilitate mock-based testing.
- Android Injection Systems - Implements injection systems that simplify wiring and threading specifically within Android components.
- Automated Dependency Wiring - Automates the wiring of service instances to minimize boilerplate configuration and decouple classes.
- Full-Stack Architectural Testing - Provides a comprehensive testing strategy combining unit, instrumentation, and simulated environment tests.
- Isolated Layer Testing - Implements testing strategies that verify the presentation, domain, and data layers independently.
- Android Environment Testing - Validates business logic and data layers using mocks within an Android-simulated test environment.
- Background Processing - Offloads heavy business logic to background threads to ensure the user interface remains responsive.
- Sample Projects - Sample app architected using different approaches
