
At a glance
kotlin
commonMain.dependencies {
implementation("com.gearui:gearui-kit:1.0.0-beta1")
}- 72 components in 6 categories — every one has a demo page in the sample app
- Design tokens with teeth — colour, radius, elevation, spacing, border and icon size are named scales; CI rejects hardcoded literals in component code
- Runtime included —
Approot wires theme, i18n, overlay host and a stabilised safe-area pipeline in one call - i18n built in — language packs resolved from a BCP 47 tag, domain-split so no class hits Android's DEX limits, and downstream libraries plug into the same pipeline
- Android · iOS · Web — one
commonMain; HarmonyOS is scaffolded, not yet built
Screenshots
Captured from the sample app on an iPhone 17 Pro simulator. Language and theme are switched at runtime from the settings page; every component follows.




Why it exists
Compose Multiplatform gives you one language for UI. It does not give you a component library that looks like a finished product on day one, or a design system that stays consistent once ten people are committing. GearUI Kit is the layer above the renderer: the components, the tokens, the runtime plumbing (overlays, safe area, keyboard, i18n) and the CI guardrails that keep all of it from drifting.
It is used in production by PrivChat's shared UI layer, which is where most of the components were shaped.
Where to go next
- Getting started — add the dependency and mount the
Approot - Platforms — what is verified on each target
- Theming & tokens — the six scales and how to read them
- Components — the full index