Interactive prototype · round 7

Edge HUD Workspace

Two identities, two modes, one workspace. Phosphor is the CRT-terminal and VCR-display world your product name already lives in; Amber is the current scheme. Coverage has been demoted from a colour to a substrate — that change applies to both.

Skin
Viewport
Layout
Upload
RETAIL REWINDC-Mart Two Notch
⇄ Synced
REVIEW
Delayed
Pinch to zoom · double-tap to fit
Coverage Motion Transactions Objects Awaiting upload No video

Same minute, four skins

The expanded ribbon rendered in every combination — the surface where the colour decision actually bites.

Investigation state

Presentation churns freely. The moment moves only when you move time.

Selected moment
Cloud storage
Presentation
View changes since moment moved
0

Coverage is now substrate

It used to be bright green — but coverage is true nearly everywhere, so colouring it meant most of the timeline shouted. It is now a quiet neutral in both skins. Motion and transactions got louder without changing their colours. This is the change I would make regardless of which skin wins.

Phosphor: the name, rendered

Green-on-black CRT with a real emission glow on live values, and a monospaced wordmark that reads as a VCR front panel. Amber is kept for motion because amber breaking a green field is the original alarm convention — it is exactly what those machines did.

Light is paper, not an inversion

Phosphor light is receipt stock with green ink; Amber light is tape-label cream. Neither is the dark theme flipped — each is a physical artefact this product already touches, which is why they hold together instead of looking washed out.

What I would pick

Phosphor dark as the default, phosphor light for daylight and printing. It carries the $50 Manager green, it is unmistakably not Digital Watchdog, and it earns the product name. Amber stays a supported theme — the token layer already supports seven.

Camera views are procedurally drawn placeholders. Skins map to CSS custom properties only — no component knows which skin is active, which is how the real implementation should work against theme-retail-rewind.css and its siblings.