Rok Horvat,

Product Designer

Design system

Bitstamp

August 2022 – Present

Overview / Context

As Bitstamp expanded its product suite and mobile offerings, our design process became increasingly complex. Each app, Basic and Pro, evolved independently, resulting in duplicated components, inconsistent behaviors, and fragmented visual language.

I initiated and led the creation of the Bitstamp Design System, which became the foundation for all future app designs. The goal was to establish a single source of truth for design and development, ensuring scalability, consistency, and efficiency across platforms.

Challenges & Motivation

Before the system, product teams faced recurring challenges:

 

  • Inconsistent UI patterns between iOS, Android, and Web, leading to visual misalignment and user confusion.
  • Slower release cycles due to repetitive design and development work.
  • Design-to-dev gaps, where subtle visual or behavioral mismatches increased QA workload.
  • Lack of a unified brand identity across apps.

 

These issues not only slowed the team but also limited our ability to scale new features or maintain a cohesive user experience across 5 million users. It became clear that a unified design system was essential to sustain product growth.

Strategy & Foundations

The system was built around four guiding principles: Consistency, Scalability, Accessibility, and Efficiency. I began by auditing existing design files, identifying reusable components, and standardizing naming conventions. This evolved into a structured component library in Figma and a set of design tokens synced directly with code via Tokens Studio, ensuring pixel-perfect parity across platforms.

 

Each component was built with scalability in mind, responsive, platform-aware, and adaptable to both Basic and Pro modes. Accessibility was also embedded from the start, ensuring color contrast compliance and flexible typography for different user contexts.

Solution

The introduction of the Bitstamp Design System transformed how we designed and shipped mobile products:

 

  • Faster design-to-development turnaround through reusable tokens and components.
  • Consistent UI across all apps, improving user trust and brand perception.
  • Easier maintenance. New features could be built faster without breaking consistency.
  • Unified design language across Basic, Pro, and later for both modes within merged mobile app.

 

This foundation allowed the team to focus more on solving user problems and less on repetitive UI work. It also created a scalable framework that future teams can easily extend as Bitstamp’s product ecosystem grows.

Process & Collaboration

Building the design system required deep collaboration between design, development, and product teams.

 

  • Tooling: I used Figma for design and Tokens Studio for variable synchronization, integrating directly with our mobile codebase.
  • Collaboration: Worked closely with three iOS and three Android developers to align design specifications with implementation. We used Jira and Trello for backlog management and design reviews.
  • Documentation & Guidelines: Created component usage guidelines, accessibility notes, and examples to ensure consistent adoption across teams.
  • Workshops & Onboarding: Hosted design system workshops with PMs and developers to explain the system’s structure, demonstrate token usage, and gather feedback for improvements.

 

Through this process, the design system became a shared language between design and engineering, reducing ambiguity and streamlining handoffs.

Details

Outcome

 

  • Faster design-to-development turnaround
  • Unified design language across web and mobile
  • Reduced visual inconsistencies and QA time
  • Stronger collaboration between design and engineering

My responsibilities

 

  • System strategy and architecture
  • Component and token definition
  • Documentation and governance setup
  • Developer collaboration

Team setup

 

  • 1 Product Designer
  • 2 Mobile Developers

Project timeline

 

  • ≈ 3 months (initial build) with continuous iteration

Rok Horvat,

Product Designer

Design system

Bitstamp

August 2022 – Present

Overview / Context

As Bitstamp expanded its product suite and mobile offerings, our design process became increasingly complex. Each app, Basic and Pro, evolved independently, resulting in duplicated components, inconsistent behaviors, and fragmented visual language.

I initiated and led the creation of the Bitstamp Design System, which became the foundation for all future app designs. The goal was to establish a single source of truth for design and development, ensuring scalability, consistency, and efficiency across platforms.

Challenges & Motivation

Before the system, product teams faced recurring challenges:

 

  • Inconsistent UI patterns between iOS, Android, and Web, leading to visual misalignment and user confusion.
  • Slower release cycles due to repetitive design and development work.
  • Design-to-dev gaps, where subtle visual or behavioral mismatches increased QA workload.
  • Lack of a unified brand identity across apps.

 

These issues not only slowed the team but also limited our ability to scale new features or maintain a cohesive user experience across 5 million users. It became clear that a unified design system was essential to sustain product growth.

Strategy & Foundations

The system was built around four guiding principles: Consistency, Scalability, Accessibility, and Efficiency. I began by auditing existing design files, identifying reusable components, and standardizing naming conventions. This evolved into a structured component library in Figma and a set of design tokens synced directly with code via Tokens Studio, ensuring pixel-perfect parity across platforms.

 

Each component was built with scalability in mind, responsive, platform-aware, and adaptable to both Basic and Pro modes. Accessibility was also embedded from the start, ensuring color contrast compliance and flexible typography for different user contexts.

Solution

The introduction of the Bitstamp Design System transformed how we designed and shipped mobile products:

 

  • Faster design-to-development turnaround through reusable tokens and components.
  • Consistent UI across all apps, improving user trust and brand perception.
  • Easier maintenance. New features could be built faster without breaking consistency.
  • Unified design language across Basic, Pro, and later for both modes within merged mobile app.

 

This foundation allowed the team to focus more on solving user problems and less on repetitive UI work. It also created a scalable framework that future teams can easily extend as Bitstamp’s product ecosystem grows.

Process & Collaboration

Building the design system required deep collaboration between design, development, and product teams.

 

  • Tooling: I used Figma for design and Tokens Studio for variable synchronization, integrating directly with our mobile codebase.
  • Collaboration: Worked closely with three iOS and three Android developers to align design specifications with implementation. We used Jira and Trello for backlog management and design reviews.
  • Documentation & Guidelines: Created component usage guidelines, accessibility notes, and examples to ensure consistent adoption across teams.
  • Workshops & Onboarding: Hosted design system workshops with PMs and developers to explain the system’s structure, demonstrate token usage, and gather feedback for improvements.

 

Through this process, the design system became a shared language between design and engineering, reducing ambiguity and streamlining handoffs.

Details

Outcome

 

  • Faster design-to-development turnaround
  • Unified design language across web and mobile
  • Reduced visual inconsistencies and QA time
  • Stronger collaboration between design and engineering

My responsibilities

 

  • System strategy and architecture
  • Component and token definition
  • Documentation and governance setup
  • Developer collaboration

Team setup

 

  • 1 Product Designer
  • 2 Mobile Developers

Project timeline

 

  • ≈ 3 months (initial build) with continuous iteration

Rok Horvat,

Product Designer

Design system

Bitstamp

August 2022 – Present

Overview / Context

As Bitstamp expanded its product suite and mobile offerings, our design process became increasingly complex. Each app, Basic and Pro, evolved independently, resulting in duplicated components, inconsistent behaviors, and fragmented visual language.

I initiated and led the creation of the Bitstamp Design System, which became the foundation for all future app designs. The goal was to establish a single source of truth for design and development, ensuring scalability, consistency, and efficiency across platforms.

Challenges & Motivation

Before the system, product teams faced recurring challenges:

 

  • Inconsistent UI patterns between iOS, Android, and Web, leading to visual misalignment and user confusion.
  • Slower release cycles due to repetitive design and development work.
  • Design-to-dev gaps, where subtle visual or behavioral mismatches increased QA workload.
  • Lack of a unified brand identity across apps.

 

These issues not only slowed the team but also limited our ability to scale new features or maintain a cohesive user experience across 5 million users. It became clear that a unified design system was essential to sustain product growth.

Strategy & Foundations

The system was built around four guiding principles: Consistency, Scalability, Accessibility, and Efficiency. I began by auditing existing design files, identifying reusable components, and standardizing naming conventions. This evolved into a structured component library in Figma and a set of design tokens synced directly with code via Tokens Studio, ensuring pixel-perfect parity across platforms.

 

Each component was built with scalability in mind, responsive, platform-aware, and adaptable to both Basic and Pro modes. Accessibility was also embedded from the start, ensuring color contrast compliance and flexible typography for different user contexts.

Process & Collaboration

Building the design system required deep collaboration between design, development, and product teams.

 

  • Tooling: I used Figma for design and Tokens Studio for variable synchronization, integrating directly with our mobile codebase.
  • Collaboration: Worked closely with three iOS and three Android developers to align design specifications with implementation. We used Jira and Trello for backlog management and design reviews.
  • Documentation & Guidelines: Created component usage guidelines, accessibility notes, and examples to ensure consistent adoption across teams.
  • Workshops & Onboarding: Hosted design system workshops with PMs and developers to explain the system’s structure, demonstrate token usage, and gather feedback for improvements.

 

Through this process, the design system became a shared language between design and engineering, reducing ambiguity and streamlining handoffs.

Solution

The introduction of the Bitstamp Design System transformed how we designed and shipped mobile products:

 

  • Faster design-to-development turnaround through reusable tokens and components.
  • Consistent UI across all apps, improving user trust and brand perception.
  • Easier maintenance. New features could be built faster without breaking consistency.
  • Unified design language across Basic, Pro, and later for both modes within merged mobile app.

 

This foundation allowed the team to focus more on solving user problems and less on repetitive UI work. It also created a scalable framework that future teams can easily extend as Bitstamp’s product ecosystem grows.

Details

Outcome

 

  • Faster design-to-development turnaround
  • Unified design language across web and mobile
  • Reduced visual inconsistencies and QA time
  • Stronger collaboration between design and engineering

My responsibilities

 

  • System strategy and architecture
  • Component and token definition
  • Documentation and governance setup
  • Developer collaboration

Team setup

 

  • 1 Product Designer
  • 2 Mobile Developers

Project timeline

 

  • ≈ 3 months (initial build) with continuous iteration