← All work Kate Shaw
← All work
Healthcare Tech · iOS & Android · 2024 – 2026

Health Dashboard & Lens Integration

Redesigning how people understand their blood pressure, from raw data to meaningful trends, and designing a completely new way to measure it.

My role Lead Product Designer → Head of Design
Platforms iOS · Android
Duration 2 years
Outcome +25% MAU · 70% ↓ drop-offs

Aktiia (later rebranded as Hilo) makes a wearable that continuously monitors blood pressure throughout the day. When I joined, the app worked, but it didn't really help! Users landed directly into a chart view of their readings, split by day, week, and month. It was accurate, clinical, and largely meaningless to most people.

The first task I was given was to design an overview screen. What followed was two years of rethinking how people relate to their own health data: not as a number to react to, but as a trend to understand.

Hilo app on a wearable device showing blood pressure monitoring and health trends
The Hilo overview — shifting the hero metric from a single reading to "time in target range."

Several hard problems, all at once

Blood pressure is not a single number

Most users came in with a cuff-at-the-doctor mental model: one reading, good or bad, done. But BP fluctuates naturally throughout the day — stress, exercise, posture, and time of day all move it. Showing raw measurements without context was causing anxiety and distrust.

A genuinely new way to measure

We integrated Hilo Lens: a cuffless blood pressure measurement taken by placing a finger directly on a phone camera lens. No established design pattern existed. Camera placement varies across every Android handset. We also had to handle keeping the finger still, ensuring hands were warm enough for a reliable signal, and recovering gracefully from errors.

Three data sources, one coherent picture

Users had readings from three sources: the Aktiia wrist band, a traditional cuff, and the new Hilo Lens. These measurements could differ significantly — for physiologically valid reasons — but users interpreted differences as the product being unreliable.

A half-finished rebrand, on a deadline

A London agency was brought in to rebrand Aktiia as Hilo. The output was incomplete: we had a name and some visual direction, but no differentiation between free and premium tiers. I applied the brand to the app under time pressure and invented the premium differentiator — the Hilo Wave — from scratch.

Designing within a certified medical device framework

Hilo was a certified medical product. Every design decision existed within a regulatory context — UI copy, visual representations of health data, and onboarding flows were all subject to documentation requirements. I was involved in the FDA application process, contributing user testing evidence and design rationale to support the submission.

A community of 700, and data from the engineering team

I used a community of 700 beta users to validate key design decisions, typically receiving around 200 responses per survey. Research focused on concept comprehension — specifically, whether users understood what "time in target range" meant, whether they found natural BP fluctuation reassuring or alarming once explained, and how they interpreted discrepancies between measurement types.

For Hilo Lens, research was observational and metric-driven. Drop-off data from the engineering team identified the specific points in the flow where users abandoned the measurement. This data drove the most important decision of the whole project.

Usability findings fed into the FDA application — documented evidence that the product could be used safely and effectively by real users.

Reframing the hero metric

Rather than leading with a reading, I proposed leading with a trend. The overview screen centred on "time in target range" — expressed as a percentage over the past week. This gave users a single, understandable answer that normalised fluctuation rather than amplifying it. 95% in target range means your blood pressure is well managed, even if one reading spiked at 2pm.

Community surveys shaped the language and visual hierarchy. We iterated on the label, the percentage framing, and the supporting copy until users could explain the metric back to us in their own words.

Hilo Lens measurement flow showing how to place a finger on the phone camera
Hilo Lens — using iPhone-specific device photography to show users precisely where to place their finger. The change that reduced drop-offs by 70%.

Designing for the most constrained case first

For Hilo Lens, I initially designed generic flows that worked across all Android handsets. Drop-off data showed consistent failure points — users couldn't reliably identify which lens to use or how to hold the phone. We made the decision to narrow scope: design specifically for iPhone first, using actual iPhone photography to show users precisely where to place their finger.

This felt like a step backwards. It wasn't.

70%
reduction in Hilo Lens drop-offs
Confirmed by engineering after switching to iPhone-specific imagery and contextual error recovery

Error recovery was designed iteratively: hand-warmth prompts, stillness cues with clear visual feedback, and step-by-step recovery screens that diagnosed the specific error rather than showing a generic failure state.

Reconciling data sources with transparency

I designed a reconciliation pattern for moments when lens, cuff, and band readings diverged significantly. Rather than hiding the difference, we surfaced it — with a plain-language explanation from Aktiia's medical team about why readings from different measurement methods naturally vary.

The counter-intuitive move was right: transparency built trust where we'd expected to need reassurance.

The Hilo Wave

The agency brief had asked for a visual differentiator between free and premium tiers but didn't deliver it. I developed the Hilo Wave: a flowing graphic element that conveyed the continuous nature of Hilo's blood pressure monitoring. It became the through-line across product and marketing, and the reason I was promoted to Head of Design in July 2025 — to own brand governance across the whole company.

Community beta research Usability testing Drop-off analysis Interaction flows Prototyping Design system build Figma Make handoff FDA regulatory documentation Stakeholder presentations

What shipped

+25%
monthly active users within 6 months
Driven by the overview redesign and features that gave users a reason to return
1

Hilo Lens shipped and iterated

A completely novel measurement interaction designed, launched, and refined — with a 70% reduction in drop-offs after narrowing to iPhone-specific design.

2

Full app rebrand across iOS and Android

Including the Hilo Wave premium differentiator, brand-consistent design system, and component library bridging Figma to engineering via Figma Make.

3

FDA application contribution

Usability evidence and design rationale submitted as part of the regulatory application — documenting that real users could use the product safely and effectively.

4

Promoted to Head of Design

Took on brand governance across product and marketing in July 2025, line-managing the brand designer and bringing in a creative director to align with the new CEO.

What I'd do differently

Education is retention. Users who didn't understand how calibration worked dropped off at a higher rate. The last project I completed was redesigning onboarding to require four calibrations over four days — making the setup feel like a meaningful start, not a gate. I should have advocated harder for it, earlier.

More data is not more value. Steps, sleep, activity — all added without a story for how they connected to blood pressure. We created data silos instead of insight. The design work I'm most proud of pushed in the opposite direction: taking complex physiological data and distilling it into one metric that changed how users felt about their own health.

Constraint produces clarity. The Hilo Lens decision to drop Android support temporarily felt like failure. It led to our best outcome. Designing for the most constrained, most common case first — then expanding — consistently outperformed designing for the general case first.