KunMinX/Jetpack-MVVM-Best-Practice
Jetpack MVVM Best Practice
This project is a reference implementation of the Model-View-ViewModel pattern using Android Jetpack components. It serves as an architecture template and layering guide, dividing application code into view, domain, and data layers to ensure a unidirectional flow of dependencies.
The implementation focuses on state management and configuration change handling. It demonstrates how to synchronize UI updates across multiple screens using shared state containers and preserves application state during transitions between portrait and landscape orientations.
The codebase covers a broad surface of Android architecture, including data flow management, the repository pattern for data abstraction, and the use of lifecycle-aware containers to maintain a single source of truth.
Features
- MVVM Architectures - Provides a reference implementation of the MVVM architecture to separate UI layout from application logic.
- Repository Patterns - Abstracts data sources into a single API to decouple business logic from network or local database implementations.
- Data Flow Orchestrators - Manages the movement of data between layers to ensure a single source of truth.
- Android Examples - Provides a reference implementation for synchronizing UI updates and exchanging data between screens using shared state containers.
- UI Data Observers - Uses observable data holders to automatically notify and update the user interface when state changes.
- UI Data Binding - Binds view components to data streams so the interface updates automatically upon source-of-truth changes.
- Android Implementations - Demonstrates a clean architecture implementation for Android with separated domain, data, and presentation layers.
- Domain Data Presentation Layers - Divides the application into view, domain, and data layers to enforce dependency inversion.
- Lifecycle-Aware State Management - Integrates Jetpack ViewModel to manage UI state and data flow during configuration changes.
- Layered Architectures - Organizes the codebase into distinct functional layers to separate concerns and ensure unidirectional data flow.
- Lifecycle-Aware State Holders - Utilizes lifecycle-aware containers to preserve UI state during configuration changes like screen rotations.
- Jetpack Navigation Components - Implements screen transitions and argument passing using the Jetpack Navigation component.
- Shared State Containers - Passes information between different screens using shared state containers for reliable communication.
- Cross-View State Synchronizations - Shares and updates information across multiple views and fragments to maintain interface consistency.
- Layout Orientation Recalculation - Preserves application state and avoids errors when switching between portrait and landscape modes.
- Screen Orientation Management - Manages display rotation and state preservation when switching between portrait and landscape orientations.
- Orientation Change Restorations - Implements patterns to preserve application state during device orientation changes.
- UI State Synchronization - Distributes updates across multiple views using a centralized data source to keep the interface consistent.
