arjncx-lang/pitch-black-launcher

Purpose and Android Entry Point

Lightest Launcher is a minimalist Android home-screen launcher focused on passive system updates, black OLED-oriented rendering, installed-app search, and immediate app launching. The Android app entry and launcher-role declaration are rooted in app/src/main/AndroidManifest.xml; runtime composition begins in app/src/main/java/com/lightest/launcher/MainActivity.kt.

UI Composition and Navigation

MainActivity.kt is the primary control surface, likely hosting the Compose launcher screen and coordinating app-list, search, HUD, settings, and app-detail interactions. UI modules are separated by responsibility:

• App-detail actions: app/src/main/java/com/lightest/launcher/ui/AppDetailDialog.kt

• Settings UI: app/src/main/java/com/lightest/launcher/ui/SettingsScreen.kt

• Visual system: app/src/main/java/com/lightest/launcher/ui/theme/Theme.kt

The resource layer supplies launcher branding, search/charging icons, and black-oriented visual assets under app/src/main/res/drawable and app/src/main/res/values.

Installed-App Discovery and Launch Flow

The domain model is app/src/main/java/com/lightest/launcher/model/AppInfo.kt. app/src/main/java/com/lightest/launcher/data/LauncherRepository.kt forms the device-package boundary: it should query Android’s package/activity APIs, create AppInfo entries, and provide the launcher’s searchable app dataset. User flow is: activity loads repository data → UI displays/filter apps → user selects an app → Android launch intent transfers control to that application.

Icon Caching Boundary

app/src/main/java/com/lightest/launcher/data/IconCache.kt isolates app-icon retrieval and reuse from app-list UI. This prevents repeated package-manager/icon decoding work during rendering and search. The cache sits between repository/package metadata and UI presentation, using AppInfo.kt identity or package-level data to resolve icons.

Passive Device-State HUD

System telemetry is represented as independent UI-state producers:

• Time: app/src/main/java/com/lightest/launcher/ui/TimeState.kt

• Battery/charging: app/src/main/java/com/lightest/launcher/ui/BatteryState.kt

• Volume: app/src/main/java/com/lightest/launcher/ui/VolumeState.kt

• Temperature and aggregate stats: app/src/main/java/com/lightest/launcher/ui/DeviceTemperature.kt, app/src/main/java/com/lightest/launcher/ui/SystemStatsState.kt

These components define the platform-event boundary. They consume Android broadcasts or system services and expose state to the activity/UI, rather than requiring a separate backend or persistent polling service. Time ticks, battery changes, and volume changes trigger focused UI state updates.

Settings Persistence

app/src/main/java/com/lightest/launcher/data/SettingsPrefs.kt is the persistence boundary for launcher preferences, consumed by SettingsScreen.kt and the root UI. It should keep user choices local to the device; the repository contains no server, API client, database, or cloud integration.

Build, Runtime, and Delivery

This is a single-module Android/Gradle project: settings.gradle.kts, root build.gradle.kts, and app/build.gradle.kts define build composition. The runtime is Android/Kotlin, with Android resources and manifest permissions/components controlling OS integration. Release optimization/obfuscation is configured through app/proguard-rules.pro and app/src/main/keepRules/rules.keep. A prebuilt distributable exists at Lightest-Launcher-v1.7.0.apk.