← back
←03 / 04→
PROJ_CDP

Cambridge Design Partnership - Mosiac

First Digital Designer · 0→1  ·  2021 – 23

Vitality Health app screens
HEALTH APP

Making health data glanceable — a 0→1 mobile app framework for a medical-device consultancy, designed once and reusable across client products.

01 · Context

Cambridge Design Partnership engineers physical medical devices; digital was a growing arm, and I was its first and only designer. My brief was to build a flexible health-app framework from scratch — demonstrated through an app which connects devices, daily health scores, trends and sleep insights.

02 · The Problem

Every client project was starting from zero: no shared patterns, no component base, no answer to "how do we show health data without alarming people?" Health metrics arrive as isolated numbers — steps, heart rate, sleep stages — that mean little on their own and can read as frightening without context.

Key insight

A health number on its own doesn't help people. It needs context: compared with what, is it good or bad, and what should I do about it?

Proto-personas

The framework has two audiences: the patient who uses the app every day, and the device maker who gives it to them as a companion to their product. Example used here: a long-acting HIV injector.

End user · Patient
D

Daniel, 34

Living with HIV · switching from daily pills to an injection every 2 months
I want to stay on track without my phone telling everyone what I'm being treated for.
Goals
  • Never miss an injection window
  • Feel in control of his treatment
  • Keep his condition private
Frustrations
  • Health apps that feel clinical or alarming
  • Notifications that reveal too much on a lock screen
  • Repeating the same details to every clinic
Needs from the app
  • Discreet app name and neutral reminders
  • Next-dose countdown and simple injector pairing
  • Easy side-effect log he can share with his clinic
Customer · Device maker
M

Maya, Digital Product Lead

Medical-device company launching an HIV autoinjector
We need a companion app at launch, but we can't build and certify a new one for every device.
Goals
  • Improve adherence, the main selling point of a long-acting treatment
  • Get to market quickly with their own branding
  • Collect usage data as evidence for clinicians and payers
Frustrations
  • Building a custom app from scratch for each device
  • Medical regulation and data-privacy requirements
  • Inconsistent experience across their product range
Needs from the framework
  • White-label theming and configurable modules
  • Built-in Bluetooth device pairing
  • Privacy and compliance patterns designed in

Proto-personas, based on the project brief and team knowledge rather than formal interviews.

03 · My Role

First and only digital designer: the framework's information architecture, wireframes, component library and visual language — plus stakeholder collaboration through release, marketing and branding of the final app.

04 · The Process

I mapped the full product as low-fidelity wireframes first:

Onboarding→Connect→Dashboard→Insights→Detail

Alongside them I defined the IA, key task flows and a starter component library. Interactive prototypes were reviewed with stakeholders and iterated through feedback sessions.

05 · Key Decisions
  • 01Design a framework, not an app — every pattern had to survive a different device, user or clinical context.
  • 02Opinionated defaults in the modular system, so screens compose instead of becoming debates.
  • 03Calm visual language — reassurance over drama for health data.
  • 04Visual trends over isolated metrics: one daily score, then progressive disclosure into detail.
06 · Constraints
One framework, many clinical contextsSensitive health data — calm, not clinicalFirst designer in a hardware-first consultancy
Connect devicesConnected and available devices are listed separately, with sync status shown, so setup is clear at a glance.
Trends over numbersOne health score with a trend line, then monthly highlights and records for people who want more detail.
Alerts with contextAlerts compare a reading with the person's usual average and explain it in plain words, alongside achievements and tips.
08 · The Impact

A reusable digital foundation for the consultancy — the Mosiac Health app shipped as its proof, and the framework's patterns, components and health-data language became the starting point for subsequent client products. Scalability designed in at the wireframe stage made the eventual product work faster, not slower.

What I Learned

Designing a framework is different from designing one app. Every decision had to work for a different device, patient and client, so I spent more time on rules and defaults than on individual screens.

With health data, how something is said matters as much as what is shown. Calm language and context made the same numbers feel reassuring instead of worrying.