How kangmin1012/composeplayground works
Project type and purpose
• This is a single-module Android application (“ComposePlayGround”) whose sole purpose is to experiment with Jetpack Compose UI patterns (bottom sheets, coordinate layouts, media permissions, custom progress animations, theming, etc.).
• There is no backend or server component; it is a client-only mobile sample project.
File structure
• Top-level files & folders:
• build.gradle.kts, settings.gradle.kts, gradle wrapper & version catalog (libs.versions.toml) → Build system (Gradle Kotlin DSL).
• app/ → Android application module
• app/src/main/
• AndroidManifest.xml → Declares activities and app metadata
• java/compose/play/ground/… → Activities grouped by feature (bottomsheet, coordinate, permission, progress, theme)
• app/src/androidTest & app/src/test → Instrumented tests & unit tests for the sample UI
• No multi-module or domain layer; all code lives in one module under feature-named packages.
Insights from the README
• It’s an experimentation playground for Compose UI, with each feature in its own Activity.
• No formal Clean Architecture or separation beyond packaging by UI feature.
• The project uses Material3 (implied by themes) and the latest target SDK (34).