How droidknights/droidknightsapp works
Project type and purpose
• This is a full-stack native Android application (“DroidKnights App”) that displays conference session, speaker, sponsor, and contributor information.
• The README describes a multi-module, layered architecture (Presentation/Domain/Data) using Kotlin, Jetpack Compose, Hilt, Retrofit, DataStore, and local JSON assets for data.
File structure
• Top-level “app” module – the Android application entry point (MainActivity, Application class).
• “feature/*” modules – each screen or feature (home, session, contributor, bookmark, setting, main).
• “core/*” modules – shared libraries:
• core/ui, core/designsystem, core/navigation (UI primitives, Compose theming, navigation model)
• core/model (shared data models)
• core/domain (use-case definitions)
• core/data-api (repository interfaces)
• core/data (implementations using Retrofit & local JSON assets)
• core/datastore (DataStore for user preferences)
• core/testing + ui-test-hilt-manifest (test utilities and Hilt test harness)
• “widget” – home-screen App Widget using the same domain/data layers.
• “build-logic” – custom Gradle plugin modules for consistent build configuration.
• CI/CD workflows under .github (unit tests, screenshots, releases).
README for additional insights
• Unidirectional data flow in UI: UI emits events up; state flows down from ViewModel
• Multi-module graph generated via Gradle + GraphViz
Elements
• App & Feature modules
• core/ui, core/designsystem, core/navigation
• core/domain, core/data-api, core/data, core/datastore
• External REST API, Local JSON Assets
• Widget module
• build-logic (build script plugin)
• UseCase → Repository → DataSource → External/Assets/DataStore
• Blue for Presentation
• Green for Domain
• Orange for Data
• Grey for Infrastructure (build-logic, CI/CD, external API)
• Labels:
• Module names, classes (e.g., BookmarkViewModel, GetSessionsUseCase, DefaultSessionRepository), data flows (JSON, Retrofit)