Shore Design System

Timeline 10 months

Team Design • Front-end Engineering • Product

The challenge

When I joined Shore, the product already served thousands of service businesses across Europe. But years of rapid growth had left the platform inconsistent, difficult to scale, and increasingly expensive to maintain. A full redesign wasn't realistic. The business needed to keep shipping new features while gradually improving the product. The challenge was to modernize the experience without disrupting development.

My role

I led the creation of Shore's first design system.

My responsibilities included:

  • Auditing the existing product
  • Defining component standards
  • Aligning design and front-end engineering
  • Creating reusable UI components
  • Supporting the redesign of new and existing features

During the project, I also joined Apple's partnership program in London, where we redesigned Shore's iOS app using the same design principles established by the system.

Building a system, not a redesign

Instead of redesigning every screen, we started by understanding the product's inconsistencies. After auditing the interface, we categorized components, identified redundant patterns, and worked closely with engineers to determine what could realistically be standardized. The result wasn't simply a UI library—it was a shared language for designers and developers. New features adopted the system immediately, while existing screens were gradually modernized as the product evolved.

Outcome

The design system became the foundation for Shore's product development.

It enabled the team to:

  • Improve consistency without a risky full redesign
  • Reuse components across web and mobile
  • Accelerate collaboration between design and engineering
  • Ship new features while continuously modernizing the product

The same principles also guided the redesign of Shore's iOS app through Apple's design partnership.