Kompound is a Kotlin Multiplatform UI component library for Android, iOS, Desktop (JVM) and Web (Wasm), built on Compose Multiplatform and the new Compose Styles API. Components take a single style parameter instead of dozens of colour and shape parameters, keep their interaction states (hovered, pressed, focused, disabled, selected, error) inside the style, and read their colours from your Material 3 theme.

Status: alpha. The API can still change before 1.0, and the Styles API itself is experimental in Compose.

Live catalog in your browser (Kotlin/Wasm; needs a recent Chrome, Edge, Firefox or Safari). It lists every component with search, category and tag filters, and interactive controls for each component's states. The same catalog runs as an Android app, an iOS app and a desktop app; build them yourself (see Build from source) or grab the Android APK and desktop installers from the Releases page.

Every component is tested on desktop and the iOS simulator (pixel checks, semantics, hit areas, state layers), has a demo, and follows the component contract.

Kompound is published to Maven Central under the namespace tech.kloos.kompound.

// build.gradle.kts of a Kotlin Multiplatform module (commonMain)
plugins {
    // Opts the module in to the Compose Styles API (see below). Available from 0.1.0-alpha03.
    id("tech.kloos.kompound") version "0.1.0-alpha03"
}
kotlin {
    sourceSets {
        commonMain.dependencies {
            implementation("tech.kloos.kompound:kompound:0.1.0-alpha03")
        }
    }
}

An Android-only or desktop-only project adds the same implementation(...) line; Gradle picks the right variant.

Why the plugin? Every Kompound composable has a style: Style parameter and Compose's Style is still experimental, so the Kotlin compiler reports "This foundation style API is experimental" for every Kompound call, even one that passes no style, unless the calling module opts in. A library cannot opt its callers in, so apply the tech.kloos.kompound plugin (above), or add the opt-in yourself, which is what the plugin does:

kotlin { compilerOptions { optIn.add("androidx.compose.foundation.style.ExperimentalFoundationStyleApi") } }

The node graph framework (editor canvas, execution engine, inspector; experimental) is a separate artifact: implementation("tech.kloos.kompound:kompound-graph:0.1.0-alpha03"). Start with docs/AGENT_GUIDE.md section 7.

Requirements

Kompound depends only on Compose Multiplatform (runtime, foundation, ui, animation, Material 3 for theme tokens and the date picker calendar). No other third-party libraries.

@Composable
fun App() {
    KompoundTheme {                         // wraps MaterialTheme; follows the system light/dark mode
        var name by remember { mutableStateOf("") }
        Column(Modifier.padding(16.dp), verticalArrangement = Arrangement.spacedBy(12.dp)) {
            KTextField(name, { name = it }, label = "Name", placeholder = "Ada Lovelace")
            KButton(onClick = { save(name) }, enabled = name.isNotBlank()) { KText("Save") }
        }
    }
}

Two things that differ from plain Material 3:

• Use KText and KIcon inside Kompound components, not Material's Text/Icon. Text inside a styled component inherits its colour and typography from the component's style; Material's Text does not read that. Icons take their tint from the surrounding component automatically.
• KompoundTheme is optional. Without it, components use the ambient MaterialTheme and light extension colours. Wrap your app in it to get dark-aware semantic colours (success, warning, info) and the spacing, motion and state-layer tokens via KompoundTheme.tokens.

Every visual component has a style: Style parameter. Your style is merged over the component's default, so you only set what you want to change, and state blocks work the same way:

import androidx.compose.foundation.style.Style
import androidx.compose.foundation.style.pressed

KButton(
    onClick = {},
    style = Style {
        background(Color(0xFF006D3B))
        pressed { background(Color(0xFF004D29)) }
    },
) { KText("Custom green") }

Defaults are exposed too (KButtonDefaults.style(variant), KTextFieldDefaults.style(), ...), so you can build on them. Colours of the default styles come from your MaterialTheme.colorScheme, so an app that is already themed needs no extra work.

KompoundTheme(
    spec = KThemePresets.Ocean,            // Default, Ocean, Forest, Sunset, Graphite, HighContrast, or KThemePresets.fromSeeds(...)
    density = KDensity.Compact,            // Compact, Comfortable (default), Spacious
    strings = KompoundStrings.German,      // default: follows the device language (en, de, fr, es, it); .copy(close = "Dismiss") edits one text
) { App() }

val imported = KThemeImport.fromMaterialThemeBuilder(jsonText)   // or fromDesignTokens(...) for Figma Tokens Studio / W3C tokens
KompoundTheme(spec = imported.theme) { App() }                   // imported.warnings lists what was not understood

Overlays are shown by calling them while they should be visible; you own the state:

var open by remember { mutableStateOf(false) }
KButton(onClick = { open = true }) { KText("Share") }
if (open) {
    KBottomSheet(onDismissRequest = { open = false }, title = "Share with") {   // sheet on phones, dialog on wide windows
        KListItem("Ada Lovelace", onClick = { open = false })
    }
}

Snackbars use a host state: val host = remember { KSnackbarHostState() }, place KSnackbarHost(host) in a KScaffold's snackbarHost slot, and call host.showSnackbar("Saved", actionLabel = "Undo") from a coroutine; it returns whether the user pressed the action.

The annotation, runtime model, KSP processor and Gradle plugins are published, so any project can mark composables as demos and get a generated registry (the mechanism the Kompound catalog itself uses):

// build.gradle.kts of the module that contains the demos
plugins { id("tech.kloos.kompound.demos") version "0.1.0-alpha03" }   // applies KSP, the processor and the dependencies

@KompoundDemo(id = "my.button", title = "My button", category = KompoundCategory.Buttons, tags = ["button"])
@Composable
fun DemoScope.MyButtonDemo() {
    val label = textControl("Label", "Click me")      // shows up as an interactive control next to the demo
    val enabled = boolControl("Enabled", true)
    KButton(onClick = {}, enabled = enabled) { KText(label) }
}

The plugin generates KompoundRegistry_<module> with every demo, metadata (title, description, tags, status) and a composable to render it. See samples/consumer for a complete example that builds against the published artifacts. The catalog app itself (catalog/shared) is not published as a library yet.

Prerequisites: JDK 17 or newer, the Android SDK (platform 37 and build-tools 37), and for the iOS app a Mac with Xcode and XcodeGen (brew install xcodegen). Create local.properties with sdk.dir=/path/to/Android/sdk if ANDROID_HOME is not set.

./gradlew :catalog:desktopApp:run                              # catalog on the desktop (fastest feedback loop)
./gradlew :catalog:webApp:wasmJsBrowserDevelopmentRun          # catalog in the browser with live reload
./gradlew :catalog:androidApp:installDebug                     # catalog on a connected device or emulator
cd catalog/iosApp && xcodegen generate && open KompoundCatalogApp.xcodeproj    # catalog on an iOS simulator

./gradlew :kompound:desktopTest :kompound:iosSimulatorArm64Test               # library tests
./gradlew :catalog:shared:desktopTest                                         # demo smoke test: renders every demo in light/dark/RTL/large font
./gradlew publishToMavenLocalAll                                              # install all artifacts into ~/.m2

Components follow a strict contract (naming, styling through Style, accessibility, tests, demos): read docs/COMPONENT_SPEC.md first. In short, a new component is a composable in kompound, a @KompoundDemo function in showcase (it appears in the catalog on its own), and tests that check its pixels, semantics and states. The PR template has the checklist.

More documentation:

• docs/AGENT_GUIDE.md: compact guide for AI coding agents (rules, component reference, graph framework, testing)
• docs/SPEC.md: architecture, decisions and the project log
• docs/COMPONENT_SPEC.md: the component contract
• docs/adr: architecture decision records (styling model, demo discovery, catalog aggregation)
• docs/RELEASING.md: how library and catalog releases work
• CHANGELOG.md

Apache License 2.0, see LICENSE. Third-party notices are in THIRD_PARTY_NOTICES.md.

Accessibility: every control has a name, a role and keyboard access (checked for every demo); see docs/KEYBOARD.md for the keyboard matrix.