Case study ·

2025

Northlight

One token file feeds Figma, the web app and the field tablet app. Components are drawn once and generated for three platforms.

Role

Design system

Client

Northlight Energy

Stack

Figma variables · CSS tokens · Storybook

Result

212 components → 64

Northlight design system: colour token docs with swatches, primary button states and 142 tokens synced to three platforms

01 — The problem

One button, drawn three times.

Three teams were drawing the same button in three tools. The web app, the field tablet app and the marketing site had drifted apart, and every redesign meant three rewrites.

Tablet · 1194 px

Northlight field tablet app showing transformer readings, a checklist, a note and an offline badge

01 —

Built from the system

The field tablet, in Northlight components

The field tablet, in Northlight components

02 — What I built

One token file, three platforms.

A single token file that feeds Figma variables, CSS custom properties and the tablet app’s theme. Components are drawn once, documented in Storybook and generated for each platform.

Pipeline · v4.12

A tokens.json file feeding Figma variables, CSS variables and Kotlin, above the v4.12 release card with 142 tokens

02 —

One file, three outputs

tokens.json to Figma, web and tablet

tokens.json to Figma, web and tablet

Component · 4 states

The Northlight sync status banner in four states with an enlarged anatomy and its tokens

03 —

Status you can trust

Sync banner and its tokens

Sync banner and its tokens

03 — What changed

One pull request, not a sprint.

The library went from 212 one-off components to 64 shared ones. A colour change now takes one pull request instead of a sprint.

64

shared components, down from 212 one-offs

142

tokens synced to Figma, web and tablet

Create a free website with Framer, the website builder loved by startups, designers and agencies.