How lawnchairlauncher/lawnicons works
File structure
• Top-level “app” module: the Android application
• src/main/kotlin/app/lawnchair/lawnicons/ui → Compose UI components & themes
• viewmodel → MVVM ViewModels
• repository & api → data layer, REST clients (GitHubContributorsAPI, IconRequestSettingsAPI), PreferenceManager
• di → dependency-injection modules
• model → domain data classes
• “svg-processor”: Kotlin CLI to consume raw SVGs & appfilter.xml, produce optimized drawables/resources
• CI/CD under .github/workflows: build APKs, optimize SVGs, Crowdin uploads
Elements
• Blue rectangles for runtime components (UI, ViewModel, Repository, API)
• Green for local storage
• Orange for external services
• Gray for build tools/scripts and CI/CD
Detail
• MVVM layer and data source
• Tooling modules (svg-processor, icontool.py) as separate processes feeding the app