How mannu691/tachiyomiat works
Main Components
• App Module: The “app” directory contains the Android application entry point (MainActivity, UI components, and configuration files) and serves as the bridge between the UI and the business logic.
• Core & Core-Metadata Modules: These directories (core, core-metadata, and submodules like core/archive and core/common) include shared functionalities, low‑level utilities, and metadata parsing/logging.
• Data Module: Contains repositories, database interactions, network services (using OkHttp, interceptors, caches), and domain data mappers to fetch and persist manga, chapters, history, source data, etc.
• Domain Module: Holds business logic, use-case interactors for chapters, manga, categories, history, and other domain models. This module encapsulates core use cases and algorithms.
• Presentation Modules: “presentation-core” and “presentation-widget” handle the UI components; they define screens (like reading, browsing, setting screens) and custom material components.
• Internationalization (i18n): Manages multilingual strings and resources using the moko-resources structure.
• Source Modules: “source-api” and “source-local” encapsulate the source fetching and parsing (i.e. integration for different online and local manga sources).
• Build & Configuration: Gradle scripts, buildSrc modules and configuration files which define the build logic and dependency injection setup to wire these layers.
Relationships and Interactions
• The “app” module acts as the entry point where the user’s interactions trigger calls to domain-level use cases.
• The Domain layer, organized in the “domain” directory, implements the business logic and uses interactors that call methods defined in the Data layer.
• The Data layer (in “data”) interacts with external resources like databases, network APIs, and file systems; it also feeds data to the Domain layer.
• UI components under “presentation-core” and “presentation-widget” render the data and react to user inputs.
• Modular separation allows easy swapping or updating of components (for example, adding new translators or sources).
• Dependency injection (as evidenced by the “di” directory in the app module and build logic modules) binds these layers together.