VDS 2.0: A Design System for screens full of data

Design System

Dev Handoff

Tokens and Guidelines

VDS 2.0 is the second version of Vecmocon's design system, rebuilt so designers, developers and AI tools can work from the same written rules.

Vecmocon's design team builds several data-heavy products at the same time. The first design system grew alongside them, made by a small team that was still learning. It had components and tokens, but nothing connecting them and nothing telling anyone how to use them. Two years and 10+ apps later, it couldn't keep up.

The rebuild started with an audit of everything we had shipped, and led to new color foundations, a semantic token model, one type scale, components with written usage rules, and tooling to keep them consistent. I led the work and built much of it myself, alongside two designers, and I'm now taking it into documentation and code with engineering.

VDS 1.0: What two years of building fast left us with

A small, young team building several products from scratch at once, learning as we went. We had something like a design system, but no foundation under it and no counterpart in engineering.

Tokens

Color tokens and components existed, with no link between them.

Engineering

Developers built their own components and tokens as convenient.

Type

No typography style. Just guesses

Handoff

Figma files with no shared language. Results were hit or miss.

Components

Basic controls that broke on new patterns, so most got detached.

QA

Manual, and under deadline it favoured function over visual correctness.

Written Guidelines

None. Everyone except the creator of a component was guessing.

Density

Our apps are data-centric. The components looked good but showed little data.

Why Rebuild Now

The old system worked well enough while we were small. Three things changed in two years.

The apps scaled

Inconsistencies became visible across products, and we had to keep checking each other's files to make sure we shipped the right thing.

Figma got new feature

New features like Slots made flexible components much easier to build and maintain.

AI arrived

We could use tools like Figma Make and Claude Design, but couldn't ship with them. They need a robust system to work from.

“We knew the rules, but couldn't feed them to AI if they weren't written anywhere.”

We started with what we already shipped.

The whole team audited the old system: the colors, the components, and the screens we had shipped. We looked for patterns in color, type, components and layout, and wrote every pattern down as a rule in plain words.

Where we found two ways of doing something, we agreed on one. We logged accessibility issues and merged in the list of improvements we'd been collecting for years. Figma, Claude and Gemini helped us shape and document our thinking.

A few pictures from the audit

Then we looked at how others do it

We studied popular design systems from other companies to see how they structure color, tokens, typography and components, and how they write and publish their guidelines.

We compared their choices with the problems from our audit and kept what fit a team of our size building data-heavy products.

ADS

Atlassian

Material Design

Google

Blade

Razorpay

Lightning

Salesforce

Spectrum

Adobe

Base

Uber

Carbon

IBM

This is VDS 2.0.

Color Primitives

Same step, same lightness

The old ramps were assembled over time with no model behind them. Ramps had 9, 12 or 13 steps, and a 500 in one color looked nothing like a 500 in another. I rebuilt every ramp in OKLCH, keeping the hues our users already knew and fixing the structure underneath. Read the full process here.

Lock the lightness scale first

One L value per step, shared by every family. Everything else stays tunable.

Evolve the hues, don't replace them

Each ramp is anchored to the hue of its old main shade. Brand teal and green sat 10° apart and merged at dark shades, so green moved to give them 20°.

Two rules for two jobs

The perfectly uniform version looked flat. Brand and neutral stay disciplined; feedback colors push chroma as far as each hue allows so status reads at a glance.

One lightness across each ramp.

One line per color. When they overlap, every step carries the same visual weight.

VDS 1.0

VDS 2.0

0.34

Lightness spread between colors at mid-ramp

One lightness across each ramp.

One line per color. When they overlap, every step carries the same visual weight.

VDS 1.0

VDS 2.0

0.34

Lightness spread between colors at mid-ramp

Color Semantics

Surfaces sit still. Containers respond.

We needed semantic tokens that were easy to pick without a manual. Looking at our screens, every fill was doing one of two jobs, so the system has two kinds of fill. On top of them sit on_fill tokens for text and icons, borders, focus and chart colors.

Typography

One typeface, 23 styles

There were no text styles before. We pulled the sizes and weights we actually used, resolved the duplicates found in the audit, and set them as one scale in Inter: display, title, label, body and caption.

display/7xl-semibold

1,284 vehicles

72

display/4xl-medium

Fleet health

36

display/2xl-medium

Battery pack 03

24

title/lg-semibold

Charging sessions

16

body/md-regular

Cell temperature crossed 45°C during the last charge cycle.

14

label/sm-medium

State of charge

12

caption/xs-medium

Updated 2 min ago

10

Components Density

More data in the same space

Fleet operators scan long tables all day. Table rows went from 48px to 40px and headers from 72px to 56px, on a spacing scale built from 2px and 4px steps.

VDS 1.0

VDS 2.0

7

Rows in view

Vehicle

Vehicle

SoC

Status

Odometer

Last seen

KA-03-EV-2291

84%

Active

12,408 km

Just now

DL-01-EV-0418

31%

Charging

8,912 km

1 min ago

MH-12-EV-7730

9%

Fault

21,077 km

4 min ago

TN-09-EV-1154

67%

Active

5,630 km

Just now

KA-05-EV-3308

92%

Idle

17,245 km

12 min ago

HR-26-EV-0981

55%

Active

9,804 km

2 min ago

DL-03-EV-6620

18%

Charging

14,390 km

6 min ago

MH-02-EV-4417

73%

Active

3,218 km

Just now

KA-01-EV-5502

40%

Idle

11,563 km

25 min ago

VDS 1.0

VDS 2.0

7

Rows in view

Vehicle

Vehicle

SoC

Status

Odometer

Last seen

KA-03-EV-2291

84%

Active

12,408 km

Just now

DL-01-EV-0418

31%

Charging

8,912 km

1 min ago

MH-12-EV-7730

9%

Fault

21,077 km

4 min ago

TN-09-EV-1154

67%

Active

5,630 km

Just now

KA-05-EV-3308

92%

Idle

17,245 km

12 min ago

HR-26-EV-0981

55%

Active

9,804 km

2 min ago

DL-03-EV-6620

18%

Charging

14,390 km

6 min ago

MH-02-EV-4417

73%

Active

3,218 km

Just now

KA-01-EV-5502

40%

Idle

11,563 km

25 min ago

Components

Flexible enough not to detach

Components now use Figma's Slots, so a card or panel accepts custom content without being detached. Every component also carries a description of do's and don'ts, so the rules travel with it into every file.

Guidelines

  • Reserve modals for blocking or high-focus workflows; use inline content, a popover, or a notification for non-blocking information.

  • Always provide a clear way to dismiss the modal unless completion is required for safety or data integrity.

  • Warn users before closing if dismissal would discard entered data.

  • In implementation, move focus into the modal, keep keyboard focus contained, support Escape when dismissal is allowed, and return focus to the trigger when closed.

  • Do not use Navigator and Counter together.

Internal Figma Plugin

Icon Component Creator

Our icons come from Google Material Symbols. Turning them into a reusable component took several manual steps, and every step was a chance for inconsistent layers and names. I built a plugin that turns a set of icons into one component, with every property we need, in one click.

Where it stands

VDS2.0 is coherent and in use, but not finished. The remaining work is about getting developers onto the same source, so what we design is what ships.

0%

Detach Rate

10+

Apps built on one system

5 s

To build an icon component, down from 2 minutes

Guideline repo

Foundation tokens and styles, components and composition rules, documented on our self-hosted Gitea server.

Code library

A component repo built from VDS 2.0 for every developer to use, so design and implementation stop drifting apart.

Fin.