Why we built Aurora
Before Aurora, our products were riddled with inconsistency—designers spent too much time recreating components, developers worked from outdated UI libraries, and teams juggled multiple design files across Sketch and Zeplin.
The process was slow, fragmented, and costly.
How We Built It
Migrated everything from Sketch + Zeplin to Figma, leveraging Figma Dev Mode to cut software costs and streamline handoffs.
We designed Aurora while launching new products, embedding it into existing ones as engineering teams were ready.
The system became the foundation for dev component libraries, ensuring 1:1 parity between design and code.
We established a governance team (Android, Web, iOS) to maintain and evolve Aurora.
The Results
60%+ reduction in design time
1 single source of truth vs. 3 separate files
Consistent UI across 9 products & 4 platforms
Automated light/dark mode toggle
Faster development with reusable components
What We Learned
Engage engineers early
(but don’t let feedback slow you down)
Balance process & speed
(too much process can hinder innovation, too little leads to chaos)
Expect ongoing iteration
(a design system is a living product, not a one-time project)
"A design system is not just a library of components—it’s a product that evolves with your team."
Take a look at how this shaped my work at Anonyome Labs 👉
View Case study