Sellsuki Design System Unifying a
Multi-Product Ecosystem
Sellsuki operates multiple products, but they lacked a shared visual language. With a small team of 4 and limited developer bandwidth, building from zero wasn't an option. We needed a system that was efficient, scalable, and dev-friendly.
The Fragmented Ecosystem
Previously, every app was an island with its own custom UI. This inconsistency slowed down design and confused users who switched between Sellsuki products.
Smart Foundation (Not Starting from Scratch)
Instead of reinventing the wheel, I audited existing component libraries that matched our tech stack. We chose a robust base to save developers from building standard components like buttons or inputs from scratch.
Branding & Multi-Theme Support
I customized the base library to fit Sellsuki’s identity using Figma Variables. This setup allowed us to switch themes instantly, supporting multiple brands and white-label client projects effortlessly.
Parity with Development
A design system is useless if code doesn't match design. I collaborated with developers to ensure our Figma components mirrored the Storybook implementation, establishing a true single source of truth.
Rules for Scalability
I didn't just design components; I defined how they behave. We prioritized reusable patterns over one-off custom solutions to keep the system maintainable long-term.
Today, Sellsuki has a unified Design System used across all products. We bridged the gap between design and dev, reduced rework, and finally look like one cohesive family.
UI Gallery
