Multi-Product Design System

Scaling consistency and clarity across mobile and desktop products

Role

Lead Product Designer

Industry

Design Systems

Duration

Ongoing

Overview

As MyCareforce expanded its product suite from a mobile app for healthcare professionals, to a web platform for institutions, to a third product called FullNurse, we needed a cohesive design system to unify experiences, streamline delivery, and scale.

I led the creation of our design system from scratch, ensuring it could flex across different devices, users and brands, while still feeling like part of the same ecosystem.

Problem

As we grew, inconsistencies started to surface. Components were rebuilt across teams. Styles diverged. And without a source of truth, it became harder to ship with speed or coherence.

We needed:

  • A shared visual language across products

  • A faster, more scalable way to design and build interfaces

  • A foundation that could support multiple platforms and brands

Overview

As MyCareforce expanded its product suite from a mobile app for healthcare professionals, to a web platform for institutions, to a third product called FullNurse, we needed a cohesive design system to unify experiences, streamline delivery, and scale.

I led the creation of our design system from scratch, ensuring it could flex across different devices, users and brands, while still feeling like part of the same ecosystem.

Problem

As we grew, inconsistencies started to surface. Components were rebuilt across teams. Styles diverged. And without a source of truth, it became harder to ship with speed or coherence.

We needed:

  • A shared visual language across products

  • A faster, more scalable way to design and build interfaces

  • A foundation that could support multiple platforms and brands

Goals

  • Ensure cross-platform consistency

  • Speed up design and development through reusable components

  • Support brand flexibility across different products

  • Improve handoff and documentation between design and dev

System Architecture

We started from zero: defining structure, logic and documentation from scratch. The system served three key products:

  • Marketplace App (mobile – professionals)

  • Enterprise Platform (desktop – institutions)

  • FullNurse (separate brand and product but part of the MyCareforce suite)

We created:

  • Shared tokens: spacing and typography

  • Modular components: reusable but adaptable to platform needs

  • Dual-brand theming: one for MyCareforce, one for FullNurse

Documentation & Tooling

We documented the entire system using Zeroheight, connecting directly with our Figma libraries. Each component came with:

  • Usage guidelines

  • Do’s and don’ts

  • Visual examples

  • Notes for developers

The result? Easier onboarding, better consistency, and fewer ambiguities during implementation.

Dev Integration & Future Vision

At first, the system was used by designers and the mobile team. But the long-term goal is to have a shared dev package — a central library where developers can simply install, import and use system components.

This approach was inspired by my previous experience at doDOC, where I helped implment and maintain their design system directly as a front-end developer.

Documentation & Tooling

We documented the entire system using Zeroheight, connecting directly with our Figma libraries. Each component came with:

  • Usage guidelines

  • Do’s and don’ts

  • Visual examples

  • Notes for developers

The result? Easier onboarding, better consistency, and fewer ambiguities during implementation.

Dev Integration & Future Vision

At first, the system was used by designers and the mobile team. But the long-term goal is to have a shared dev package — a central library where developers can simply install, import and use system components.

This approach was inspired by my previous experience at doDOC, where I helped implment and maintain their design system directly as a front-end developer.

Learnings

  • Building a system that works across platforms requires thoughtful flexibility, not everything should be rigidly uniform

  • Documentation is a design deliverable

  • A good design system isn’t just about saving time, it’s about enabling better work, together

A design system is not a project. It’s a product that supports every other one.

Learnings

  • Building a system that works across platforms requires thoughtful flexibility, not everything should be rigidly uniform

  • Documentation is a design deliverable

  • A good design system isn’t just about saving time, it’s about enabling better work, together

A design system is not a project. It’s a product that supports every other one.

Beatriz Geirinhas

Copyright 2025 by Beatriz Geirinhas

Beatriz Geirinhas


Copyright 2025 by Beatriz Geirinhas

Beatriz Geirinhas

Copyright 2025 by Beatriz Geirinhas