Feature Library

Effects switchboard

0.04 CPU ms
A still of the Effects switchboard demo
Still
The live demo starts when it’s in view.Hover the cards, press Ping, open the FX tab on the right or press E · turn the dials under Tune (drag, arrows, or type), double-click one to reset it

One place that says which of an app’s effects are on.

What it costs a frame

0.04 ms
GPU
not used
CPU, median
0.04 ms
CPU, 95th pct
0.07 ms
Draw calls
0
Weight
Light

Measured 3 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 156, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured with every group at its default (sound off): the per-frame cost is the ambient drift moving three blurred layers and the counters easing. The switchboard itself does nothing per frame; it only acts when a switch changes. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed0.040.07
apple · Apple A19 Proin a browser tab · 16 November 2026not timed0.080.12
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed0.060.11

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Apps with ambient or decorative effects
  2. Design reviews (see a look with and without its effects)
  3. Motion and sound preferences
  4. Calm modes
  5. Kiosks and demos
  6. A tuning panel for an effect’s parameters
  7. Settings with recommended values and a reset

Pitfalls, in brief

  1. The switchboard only says what is on: each effect has to ask (on(group) each frame, or subscribe) or be gated in CSS through reflectEffects.
  2. Gate what someone asked for differently from decoration: a confirmation or a result the person clicked for should not belong to a group, or switching effects off hides feedback they need.
  3. Turning Links off should leave links recognisable (a plain underline), not remove them; switch the flourish, never the affordance.
  4. Reduced motion sets Motion’s default only.
  5. Browsers only let audio start after a gesture: create the AudioContext on the first click that plays a sound, and start Sound off.
5 more in brief
  1. The E hotkey listens on the window and skips inputs, text areas and contenteditable; pass hotkey: null if E already means something in your app.
  2. Import knob-table.base.css, then knob-table.css (or your own look): without the base the dials have no size, no fill and no pointer, and a drag on one scrolls the page on touch.
  3. A dial takes its drags (touch-action: none) and turns with a drag up or right, not round: a circular drag needs the pointer’s angle round a centre that small dials make jumpy.
  4. Saved values are cleaned against the table on load (unknown ids dropped, numbers snapped into range), so a table that changes its ranges never starts out of range; a renamed id starts again at its recommended value.
  5. onChange runs for every change the person makes, not for set(…, { silent: true }): use silent when your app moved the value itself (its own controls, an undo), or the two will echo.
10 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From HaTac. Fully custom code.

WAI-ARIA Authoring Practices Guide (W3C): The slider pattern for each dial: role="slider", its value attributes and keys.

domsettingsaccessibilityreduced motionlocalStorageshadow domkeyboardknobsdialsslidersrotarytuningparametersno dependencies

Near it in the frame