Concept · Original study · Simulated data

One design system, console to phone

Concept: the mission monitor console and a phone side by side. Both show the same Link degraded chip, the same alert row for vehicle C, and the same escalation card asking the supervisor to approve a return or hold.
Concept: the mission monitor console, cropped, beside a phone. Both show the same Link degraded chip, the same alert row for vehicle C, and the same escalation card asking the supervisor to approve a return or hold.

Concept draft · simulated data

An original concept study: what a small design system needs so one signal reads the same way on a ground console and on a phone (iOS or Android). It builds on the mission monitor concept. The vehicles, tokens and data are all simulated.

The problem

One signal, two surfaces, a degraded link. When vehicle C goes quiet, the console and the phone have to say the same thing: how old the data is, what is estimated, and who decides next. If they drift apart, the same moment can look calm on one screen and urgent on the other.

The system in one view

Concept token and component sheet: six colour swatches (ink, ink deep, paper, chartreuse, mute, soft) with hex values, a four-step type scale, spacing steps of 4 to 24, two corner radii, two depth levels, and the status chip, alert row, link-quality meter and escalation card.

Concept draft · simulated data

Tokens: a restrained palette of charcoal, warm white and chartreuse, with chartreuse used only for state (live, selected, needs a decision), never for decoration. One type scale, a short spacing scale, two corner radii, and two depth levels: flat for panels and rows, raised only for decision cards.

Components: a status chip, an alert row, an escalation card and a link-quality meter. Each is defined once and used on both surfaces.

State rules

Concept state rules: fresh, stale, estimated and lost data, each with one marker and one data-age label, shown identically in a console row and a phone row.

Concept draft · simulated data

Fresh, stale, estimated and lost data each have one expression: a marker shape, a way of stating data age, and a colour. Both surfaces use the same one, so “last seen 38 s ago” means the same thing wherever it appears.

What changes between breakpoints, and what must not

May change: layout, density, how many alerts are shown, and the size of the map.

Must not change: marker shapes, data-age wording, state colour, and the two decision actions on the escalation card.

Design questions the concept explores

Shared tokens or shared components: rather than sharing only colour and type, the concept shares the components too, so a state looks the same everywhere.

Device fit or fixed states: the layout follows the device, but how a state is expressed does not, so a phone never shows a calmer version of the same moment.

Where the accent goes: rather than using chartreuse for brand, it is reserved for state, so it always means something.

Not shown in this concept

Light and dark themes, accessibility testing, motion, tablet and watch layouts, and how the system would be versioned and maintained. This is a concept with simulated data, not a shipped product.

About

Design leader shaping digital products that scale. 20+ years in UX, games, and SaaS.

Social

© 2025 Greg Herboek · Designed in Austin · All rights reserved.

About

Design leader shaping digital products that scale. 20+ years in UX, games, and SaaS.

Social

© 2025 Greg Herboek · Designed in Austin · All rights reserved.

About

Design leader shaping digital products that scale. 20+ years in UX, games, and SaaS.

Social

© 2025 Greg Herboek · Designed in Austin · All rights reserved.