How flixclusiveorg/flixclusive works
Project type and purpose
• This is an Android application (mobile + TV) called “Flixclusive” using a modularized, Clean-Architecture approach.
• It uses Jetpack Compose for UI, Hilt for DI, Room for local persistence, DataStore for preferences, Retrofit/OkHttp for network, and a background update service.
File structure and layers
• Top-level Gradle modules:
• app – hosts the Android application, entry points (MobileActivity, TvActivity), navigation setup, Crash reporting, BuildConfig
• service – background Android Service for update notifications
• core – cross-cutting libraries (network, database, datastore, presentation, UI components, testing, navigation, drawables, strings)
• domain – business-logic use-case modules (catalog, database, provider, tmdb)
• data – repository implementations for domain (database, provider, tmdb)
• feature – UI feature modules (per-screen: mobile home, film, search, settings, etc., and TV features)
• The project follows MVVM + Clean Architecture:
UI (feature & core/presentation) → ViewModel → Domain use-cases → Data repositories → Data sources (Room, DataStore, network).
README insights
• Confirms it’s purely a streaming-links client (no hosting).
• CI/Quality badges indicate use of CI pipelines (GitHub Actions) and SonarCloud.
Final advice
• Be exhaustive: include each module and major sub-component (DI modules, network monitors, CrashHandler, updater service).
• Modules logically (e.g., all domain modules in one “Domain Layer”).