Product expansion:
Alongside the redesign and design-system work, I continued designing and expanding the product across its main experiences, including the homepage, coin pages, coin categories and listings, profile, wallet, deposits, withdrawals, referrals, notifications, and login. I also designed new areas that were not part of the original product, including KYC and the blog. The homepage and individual coin pages received broader redesigns to better present the product and its content, while transaction-related flows such as deposits and withdrawals were refined as the product evolved.
Results:
The project evolved from a basic, partially implemented product into a more complete MVP and subsequently a more stable and expandable product. The design work also established a stronger foundation for continued development: reusable components replaced much of the earlier page-specific approach, visual styles became more structured, and the design and engineering structures became more closely aligned. The next phase is to continue organizing the Figma files and component architecture as the product grows, keeping the design system maintainable as new features and product areas are introduced.
Reflection:
The token-based system was built retroactively, on top of components that had already been implemented ad hoc during the MVP phase. That meant part of the work wasn't just designing the right structure, but reconciling it with decisions engineering had already made — which took longer than if the tiered token architecture had been the starting point from day one. If I were starting Rodeo's design system today, I'd establish the primitive/semantic token layers before the first component was built, rather than introducing that structure once the product had already grown. It would have saved the reconciliation work between Figma and the existing codebase, and avoided the inconsistencies that came from components being created independently early on.