repository·main·Indexed 12 days ago
https://github.com/android/nowinandroidA sample Android application demonstrating best practices in modular architecture. The project features a layered structure consisting of feature modules, core modules (such as :core:data, :core:domain, and :core:designsystem), and a sync module. It utilizes a custom 'build-logic' included build with composable convention plugins for Gradle configuration, including specific plugins for Android applications, libraries, and Jetpack Compose.
:core:datastore-test is an Android library module designed to provide testing utilities for DataStore. It is part of the :core layer of the project and depends on :core:datastore and :core:common to facilitate testing DataStore implementations.:app-nia-catalog module is an Android application that serves as a catalog for the project. It depends on the :core:designsystem and :core:ui modules. The :core:ui module, in turn, depends on :core:analytics, :core:designsystem, and :core:model.:feature:bookmarks:api module is an Android library that serves as the public API surface for the bookmarks feature. It is part of the :feature:bookmarks feature set and depends on the :core:navigation module to facilitate navigation within the bookmarks context.:feature:foryou:api module is an Android library that serves as the public API surface for the 'For You' feature. It is part of the :feature layer and depends on the :core:navigation module. This separation allows other modules to interact with the 'For You' feature via its API without needing to depend on its internal implementation details.The :feature:bookmarks:impl module is the implementation layer for the bookmarks feature. It contains the internal logic, UI components, and data handling required to support bookmarking functionality within the app.
In the project's modular architecture, this module is separated from its public API (:feature:bookmarks:api) to ensure that implementation details are not leaked to other features. It depends on several core modules for data management, design system components, and UI building blocks.
:core:notifications module is an Android library within the :core layer of the project. It is responsible for handling notification-related logic. It depends on :core:model for data structures and has a transitive dependency on :core:common.:core:model module is a pure JVM library within the :core layer of the project. It serves as a central location for defining domain models that are shared across different layers and features of the application. Because it is a JVM library, it does not depend on Android-specific APIs, making it highly portable and suitable for use in both Android and pure Kotlin/JVM environments.:core:navigation module is a core Android library within the project responsible for handling navigation logic. It serves as a centralized library that other modules (such as feature modules or the application module) depend on to facilitate navigation across the app.:lint module in this project is responsible for managing linting configurations and rules. It serves as a centralized location for linting logic that is applied across the repository to ensure code quality and consistency.The :core:database module is an Android library within the :core layer of the project. It is responsible for database-related concerns and depends on the :core:model JVM library.
In the project's architecture, :core:database provides the data persistence implementation, while :core:model defines the data structures used across the application.
The :core:data module serves as the central data layer orchestration component within the :core layer of the project. It acts as a mediator that integrates various data sources, including local databases, datastores, and network services, to provide a unified data interface for the rest of the application.
To implement or extend data logic, understand that :core:data depends on the following modules:
Direct Dependencies:
:core:analytics (via implementation/api):core:common (via implementation/api):core:database (via implementation/api):core:datastore (via implementation/api):core:network (via implementation/api):core:notifications (via implementation/api)Transitive/Downstream Dependencies (via its dependencies):
:core:model (used by :core:database, :core:datastore, :core:network, and :core:notifications):core:datastore-proto (used by :core:datastore):benchmarks module is an android-test type module used for performance benchmarking within the project. It interacts with the :app module via baselineProfile and receives testedApks from it. This module is central to measuring and maintaining the performance characteristics of the application.