Skip to content

Expressions

One API. Three ways to build it.

Every Prism component shares one set of props and one behaviour contract: the same roles, the same keys, the same focus. On top of that sit three complete design languages, each built with a different technique. The product below is written once. Switch it.

Expression

Enter a full email address

Send it
Volume
Daily digest
Mentions only
Changes apply to every device

The same curve

A spring, compiled to CSS

━ Luminous: requestAnimationFrame, k 180, d 22, every frame in JS• Reserved: the same constants compiled once into 40 CSS linear() stopssettle 483ms · overshoot 0.1% · glow spring (k 120, d 18) 717ms

Luminous runs its springs in JavaScript, every frame. Reserved does not run them at all. It takes the same hand-tuned stiffness and damping, simulates the spring once, and hands the browser a CSS linear() easing that traces the identical curve, overshoot included. The animation then runs on the compositor with no script.

The tuning stays the single source of truth: change the constants and both expressions move the same new way. Editorial is the control: no easing at all, every state change instant.

Written once

The product code doesn't change

<Tabs id="settings" label="Settings sections" tabs={sections} value={tab} onChange={setTab} />
<TextField label="Email" type="email" value={email} onChange={setEmail} error={error} />
<Select label="Send it" value={frequency} onChange={setFrequency} options={frequencies} />
<Slider label="Volume" value={volume} onChange={setVolume} />
<Switch label="Daily digest" checked={digest} onChange={setDigest} />
<Button>Save changes</Button>

Each expression is held to one contract: a switch is a switch to a screen reader, tabs move with the arrow keys, a slider takes Page Up and Home, a select opens with Enter and closes with Escape. The same automated tests run against all three.