How komikku-app/anikku works
Project Type & Purpose
• Anikku is a multi‑module Android application (Kotlin + Jetpack Compose) for discovering and watching anime.
• It follows a Clean‑Architecture approach (layered modules for presentation, domain, data) and ships as a feature‑rich client with local database, network calls, file I/O, sync, extensions, and widgets.
Key Modules & Patterns
• app: Android application entry point (UI hosts, Compose screens, ViewModels, DI wiring, WorkManager jobs).
• presentation‑core / presentation‑widget: Shared Compose UI components & Glance widgets.
• domain: Business logic (use‑case interactors, models, repository interfaces).
• data: Data layer implementations (SQLDelight repositories, mappers, network services).
• source‑api / source‑local: Extension‑point modules for pluggable remote and local “sources”.
• core‑common / core‑archive / core‑metadata: Utility and shared network, archive (CBZ), metadata models.
• i18n modules: Multi‑platform resource providers.
• buildSrc: Centralized Gradle conventions.
• DI: DomainModule, AppModule, PreferenceModule – likely using Koin or Dagger/Hilt for dependency injection.
• MVVM: ViewModels in app module talk to domain use‑cases.
External Services & Infrastructure
• Remote anime sources: HTTP parsers (source‑api), trackers (AniList, MyAnimeList, Kitsu, Simkl, Bangumi).
• Backup & Sync: Google Drive, SyncYomi services.
• Discord Rich Presence via RPC service.
• Torrent server API.
• Local persistence: SQLDelight database, SharedPreferences/DataStore.
• File I/O: CBZ/unzip, image caching (Coil), downloaded media files.
• WorkManager: background jobs for backup, library updates, syncing, downloads.