How bl4ckswordsman/cerberustiles works
Main Components
• App Module – This is the core of the Android application.
• Activities – The project defines several UI entry points such as MainActivity, OverlayActivity, and ToggleActivity. Represent these as separate components, indicating that they form the main user interface.
• Quick Settings Tiles Services – The package “quicksettingstiles” contains services like AdaptiveBrightnessTileService that integrate with Android’s quick settings. Add these as separate modular components.
• UI Components & Themes – Under the “ui” and “theme” directories, the project defines various UI elements (Components.kt, MainScreen.kt, dialogs, and styling information). Group these into a User Interface Layer.
• Helper Utilities & Business Logic – Classes such as SettingsUtils, VersionManager, Constants, and LicencesInfo encapsulate application logic. Represent these as underlying business logic or helper modules that support the UI.
• Navigation – The “navbar” package (e.g., BottomNavBar) represents navigation-related components.
• Resources – Drawable, mipmap, XML, layouts, and assets (like the open_source_licenses.html file) should be shown as part of the resource management layer.
Out Interactions & Relationships
• That the Quick Settings Tile Services (like AdaptiveBrightnessTileService) interact directly with Android’s system services to update system settings.
Architectural Patterns
• Although not explicitly mentioned as MVVM or MVP, the separation between UI (activities, Fragments, dialogs) and business logic (utility classes, version management) follows common Android architectural practices.
• That there’s a clear separation between presentation (UI/activities) and logic (services/utilities), which may evolve into a more formal design pattern with further development.
Relevant Technologies and Frameworks
• Kotlin as the primary programming language.
• Android SDK components (activities, services, resources).
• Gradle as the build system, including the Kotlin DSL (build.gradle.kts).
• GitHub Actions (workflows for code quality, builds, and releases) to ensure continuous integration and deployment.
• (Optional) CodeQL for security and quality analysis.