Skip to content
Cabin

Develop

Build on Cabin

Developer documentation lives on the docs site — this marketing surface stays focused on the product story. Deep-link when you are ready to integrate.

  1. Step 1

    Read the contracts

    Start with vision, MVP v0.1, and ADR 0006 (Material 3 base, six looks, three tiers) so library scope stays deliberate and thin.

  2. Step 2

    Tokens, compliance, chrome

    Alpha: cabin-tokens, cabin-compliance, cabin-views (Theme Kit + System/Status bars). Experimental: cabin-foundation, cabin-compose (Material 3 theme, looks, kit), cabin-screens (Home / Media / Climate), cabin-gauges.

  3. Step 3

    Pick your consumption path

    Apps: Gradle / Maven. SystemUI and build-tree: Soong Android.bp — Views-first, never Gradle-implementation into platform chrome. Compose and screens are app dependencies only.

Dual distribution

Thin artifacts by design. Samples, catalog, and websites never leak into product images.

App developers
Gradle → Maven
cabin-tokens · cabin-compliance · cabin-views · cabin-compose · cabin-screens
Platform / SystemUI
Soong → Android.bp
CabinTokens · CabinCompliance · CabinViews
Apps in the tree: CabinCompose · CabinScreens

Toward external/cabin

The long-term target is an AOSP drop next to car-ui-lib and the AAOS OEM design tokens. Look roles use the same Material 3 names as those tokens.

Verified
All seven Soong modules compile with an AOSP 17 tree's own toolchain, against AOSP prebuilts only.
Enforced
Apache-2.0 headers, no GMS or bundled fonts, token-only color, thin Soong deps — checked by the quality pipeline in CI.
Planned
A full m build in a clean tree, a public API dump, and one OEM design token RRO per look.

See the kit running in the catalog Showcase: Home, Media, and Climate in each look, day and night, stepping from Parked to Restricted. Sample only — never a cabin-* or SystemUI dependency.