Open to senior product roles

One freelance project at a time

Sydney 10:06 am

Open to senior product roles

One freelance project at a time

Sydney 10:06 am

Open to roles

Sydney 10:06 am

Oda

Design system

2024

One system for three platforms

Three apps had grown three different sets of buttons. Oda gave them one set of tokens and components that each platform could still render in its own way.

Role

Role

Design system lead

Team

Team

3 designers, 4 engineers

Timeline

Timeline

9 months

Result

Result

112

components across web, iOS and Android

The problem

The problem

The web app, the iOS app and the Android app were built by separate teams who rarely talked. We counted 41 button styles between them.

A simple colour change took three tickets and three weeks, and every new screen started with someone redrawing a component that already existed somewhere else.

What I did

What I did

I started with tokens, not components: colour, type, spacing and radius, named by purpose instead of by value. Each platform team mapped the tokens to its own components, so iOS could still feel like iOS.

Then we rebuilt the most used components together, one a week, with an engineer from each platform in the room.

Component states with their spacing and token names

Outcome

Outcome

A brand colour change now takes one pull request instead of three tickets, and new screens ship about a week faster because nobody redraws a button.

The token table, light and dark

What I learned

What I learned

A design system is mostly agreements between people. The components were the easy part.

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