Rodeo

B2C crypto exchange focused on trading and onboarding

Crypto

2024–2026

Summery

Rodeo is a decentralized crypto exchange that I joined with an existing, partially implemented product based on an older design. My initial responsibility was to redesign and expand the product while staying close enough to the existing implementation to avoid unnecessary development effort and keep the team on track for the MVP. After delivering the MVP, my focus expanded from individual product screens to building a more scalable design foundation, including a structured component library, design tokens, styles, and a more consistent design system.

CLIENT

Ragge Company

ROLE

Product Designer

SCOPE / PLATFORM

Web + Mobile

Challenge

When I joined Rodeo, the product already had a basic implementation based on an older design. The UI needed a visual and UX update, while some existing experiences also needed to reflect newer financial requirements.

The main constraint was time. Rebuilding the product independently from the existing implementation would have created additional development work and potentially slowed down the MVP. The redesign therefore had to improve the experience while remaining practical to implement within the existing technical foundation.

There was also no established design system. Components had been created as needed during the product development process, which resulted in inconsistent naming, duplicated components, limited scalability, and a mismatch between the design components and their technical counterparts.

Approach

I started by working within the existing product foundation rather than treating the redesign as a completely new product. This allowed us to move quickly toward the MVP while keeping the new designs compatible with the existing implementation.

During the MVP phase, I gradually built reusable components as part of the product design work. This helped keep the growing number of screens consistent without introducing unnecessary complexity while the product was still evolving.

Once the MVP was delivered, I shifted more of the focus toward formalizing this foundation into a more structured design system. I reviewed the existing components and styles, standardized their structure and naming, and introduced tokens and reusable patterns across the product.

An important part of this work was aligning the design structure more closely with the technical implementation, making it easier for design and engineering to work from a shared component structure.

Solution

From page-specific components to reusable patterns

As the product grew, creating separate components for individual sections was becoming increasingly difficult to maintain. I reorganized the component structure around reusable patterns and variants so that new product areas could build on existing components instead of introducing new versions of the same UI.

Building the visual foundation

I structured the design tokens in two tiers: a primitive layer defining raw values (colors, spacing units, typography scales), and a semantic layer mapping those primitives to contextual use — for example, defining which of the base colors served as the border color in different states. Separating these layers meant a single change at the primitive level could propagate consistently across the product, instead of requiring manual updates across every component.

The component library grew to 40+ components, each structured around multiple variants and states (primary/secondary, hover/disabled, etc.), replacing the earlier pattern of building one-off components per page.

Standardizing components and states

The component library was reorganized with clearer naming and structure. Common UI elements such as buttons, inputs, dropdowns, modals, and other interface patterns were structured around reusable variants and states rather than being created separately for each page.

Aligning design with development

Because the initial design structure did not always correspond to the components already implemented by engineering, I worked toward a closer mapping between the Figma component structure and the technical implementation. This made the design system more practical for an existing product rather than treating it as a separate design artifact.

Outcome

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.

Create a free website with Framer, the website builder loved by startups, designers and agencies.