← Work
Design systems
Oyster
Oyster · UI system

Making UI easier to use and easier to ship.

The guidelines had piled up shades, tints and local variations — every one another decision. I cut them down to a palette of roles and worked with Frontend to turn reusable patterns into a production component library.

1 model
shared by Design and Frontend
Oyster color palette
Fewer options, faster decisions.
My seat
Product Designer
Built alongside
2 Frontend Engineers
Focus
UI system · Components · Onboarding
Layers
Foundation → Components → Patterns → Flows
What I did
What changed

From color options to a shared component model

01

Audit the legacy system

A broad shade and tint matrix with many similar choices and room for inconsistency.

02

Simplify the palette

Reduced to primary, secondary and complementary colors, each with a clear purpose.

03

Align design with code

Worked with two Frontend Engineers so Figma and production shared one component model.

04

Apply the system to onboarding

Applied the updated design system to the constantly evolving onboarding experience, making it easier to maintain and adapt as requirements changed.    

01

Less reinvention

Common patterns could be reused instead of rebuilt.

02

Faster iteration

Small onboarding changes could happen at component level.

03

Shared language

Design and Frontend worked from the same component logic.

04

Easier revamps

Larger changes were simpler because flows were already componentized.

Three moves behind the system

Color roles

Colors as roles

A smaller palette in three tiers, each color with a clear job.

Design to Frontend component mapping

One component logic

Figma and production built from the same model, not interpreted from a reference.

Onboarding steps from one shell

Onboarding as a stress test

Same shell, different fields, new states — change the piece, not the whole screen.

Want the full story?
Get in touch.

Color system
Component library
Design–frontend alignment
Onboarding