Aurum, set for Android.

Frank Ruhl Libre · Inter · JetBrains Mono — the system’s three voices, in Jetpack Compose.

Jar’s design system, generated from the same Figma file as Aurum for iOS. Every component, every token, every device size — current with what ships on main.

Browse the components Download the catalog APK
41components
372rendered states
89icons × 2 weights
14families

What shipped in v0.3.29

30 Jul 2026
  • AurumIcons.Navigation.CaretBold{Up,Down,Left,Right} (+ Filled). Their masters have been sitting in the canonical icon sheet (5130:35416) without code counterparts, so the sheet↔catalog contract was one-sided. Single-weight in Figma, so both weights resolve to the same drawable — the same convention the existing Caret family uses. The heavier caret is what CaretCircleRight is built from, which is where consumers keep needing it.
  • Catalog gallery now lists the whole Caret family. CaretUp/Down/Left/Right shipped in code but were never added to IconGallery, so they were invisible in the catalog; listed now alongside the new bold set.
  • AurumSectionHeaderAction.Link now renders neutral-subtle, matching its Figma master (5442:462). The link action was styled identically to the text action — Title/XS-SemiBold in interactive.textPrimaryNormal (brand purple) with a 20dp iconPrimaryNormal chevron — so "View All / See More" links shouted as loudly as the section title and were indistinguishable from a brand text-button. The sheet's action link layer specifies Body/S-Medium in interactive.textNeutralSubtle with a 12dp interactive.iconNeutralSubtle chevron; the component now follows it. TextAction is unchanged and remains the brand-emphasis option. Consumer impact: every existing Link action becomes grey and one step smaller — intended, but visible. aurum-ios mirrors this in 0.2.3.

Read the full changelog

How a change ships

The diff is visual

Any component that moves fails its Roborazzi baseline. The PR shows the pixel diff across six device and font-scale combinations — decide if the change is intentional.

CI re-records

Approving means adding the record-baselines label. CI re-records on Ubuntu (never a laptop) and commits the new baselines to the PR.

The portal follows

Every merge to main regenerates this site, the manifest and the catalog APK — nothing here is written by hand.

One Figma file

Every Figma-backed component carries a .figma.kt mapping, published to Dev Mode from each release tag with exact token references like Aurum.colors.surface.bgPageBase.

Two Figma Community plugins close the loop: Aurum Compose ↗ turns any selected frame into idiomatic Compose, and Aurum Token Sync ↗ keeps codeSyntax.ANDROID on every variable.

Open the Aurum Figma file ↗

Two platforms, one contract

The token layer is generated from the same Figma Variable exports as the SwiftUI library — same names, same values, same icon set. If it exists here as Aurum.space.s16, it exists on iOS too.

Agents read this portal as data: the full catalog ships as a manifest at /data/manifest.json.

Browse Aurum for iOS ↗

Contents