Design System - Chassis

Development of component libraries

CROSS PLATFORM

Problem

Across three product teams who worked on our major white-labelled product, the designs were misaligned and inconsistent. We needed a solution. This inconsistency was creating a lot of technical debt too. We needed a solution that would have made us all more productive, design-consistent and free of design and tech debt.

Solution

I developed a component library in collaboration with designers and developers. It ensured clarity on component usage for both teams. All assets were accessible and scalable, supporting use in other apps, including our white-labeled product for external companies.

A preview of a component library in Figma

Documentation

To keep both the other designers and developers up to date with any changes to our Design System, I utilised ZeroHeight and created appropriate assets to create a design guide.

A preview of The Floow's documentation in ZeroHeight

The Design System was accessible

I was responsible for making the components Iā€™d been working conform to the WCAG 2.1 AA standard. This included creating educational materials for the rest of the team to follow in ZeroHeight.

A page on using "spacing" in FloowDrive design

Asset libraries

All libraries and components were created in Figma. Since FloowDrive is an app that can be white-labelled, we used certain Figma plugins in order to make all our libraries and component libraries customisable.

""

Typography library

""

Components library (example)