Phoenix (Design System)
About
-
Product designer
This is a complete revamp of Birdeye’s design system. Our goal is to remove and replace all old and inconsistent design systems by rebuilding components and defining their use-cases.
What changed?
Replacement of all old and inconsistent designs in the platform
New, updated component styles
Defined component usages
Consistency in platform
After the design system was complete, our platform slowly became more cohesive, making it easier for users to get accustomed to all pages. With the previous experience of having differently sized buttons, it was difficult for users to predict and access certain products or features.
Faster designing process
What differed the most from the previous design systems was that we were able to clearly define the use case of each component. This helped reduce the cognitive load of the design process as well as onboarding incoming designers.
Increased project handovers
The faster design process resulted in an increase in design reviews, so it was faster to hand off projects.
What I learned
Limitations and use-cases
Component states
Keep in mind about responsiveness and the pixel-perfect specs for all components.
All possible states in frequently used components (ex. active, disabled, focused, etc.) and their interaction design.