Cue Health

From COVID Testing to Full At-Home Health (2021–23)

Cue app — diagnostics screen Cue app — care screen Cue app — prescription screen

Overview & Scope

Cue Health launched as a COVID-19 rapid testing platform built around their proprietary molecular diagnostic device. As the acute pandemic phase subsided, the business needed to evolve — or risk irrelevance as a single-use tool.

My role was to help design the platform's expansion into a comprehensive at-home health experience spanning diagnostics, telehealth, and prescription delivery — transforming Cue from a testing app into a full-circle health platform.

Objective

Design a unified mobile experience that guided users seamlessly from testing, through results interpretation, into care options — and for appropriate diagnoses, directly to telehealth consultation and prescription fulfillment. Every new surface needed to feel native to the existing app without requiring a full rebuild of the foundation.

My Role

As Product Designer (in-house), I was responsible for:

  • Designing new user flows for Care, Treatment, and Rx Checkout experiences
  • Extending the existing design system to support health record categories, condition classification, and prescription states
  • Partnering with product, clinical, and engineering to navigate regulatory and clinical accuracy constraints
  • Prototyping and iterating based on usability feedback and clinical team review

Platform

Mobile (iOS / Android) — consumer B2C, direct-to-patient health care. Integration with Cue Reader hardware device for diagnostics. Telehealth provider network for care escalation.

1.

Platform Evolution: Ingress & Onboarding

From Single-Test to Health Platform

The original Cue app was built around a single, linear flow: run a test, get a result. Expanding into a health platform required rethinking the app's core architecture. Users needed to understand that Cue was now more than a diagnostic tool — it was a health companion with continuity across time.

The first design challenge was ingress: how users enter the new platform surfaces. Key questions included:

  • How do users who completed a test get surfaced with relevant care options without feeling upsold?
  • How does the platform introduce new capabilities without overwhelming users who came for a simple test result?
  • How do we preserve the quick-action simplicity of the testing flow while adding depth for users ready for more?
User flow — platform ingress and onboarding

App Screens

Cue app screen Cue app screen Cue app screen
2.

Diagnostics: Test Results & Health History

Test Results Flow

The test results experience was the most established part of the platform, but it needed to evolve from a static result display into a decision point — one that could route users into appropriate care based on what the test found.

Design priorities for the results flow:

  • Clinical clarity first — Results needed to be unambiguous, especially for positive diagnoses. Color, iconography, and language were all reviewed by the clinical team
  • Contextual next steps — Positive results surface care options; negative results surface preventive health content
  • Health history continuity — All results persist in a browsable health record, giving users a longitudinal view of their testing history
User flow — test results and health history

Platform App Screens

App screen App screen App screen App screen
3.

Care: Telehealth & Treatment

Care Categorization

The Care experience was the most clinically complex surface to design. Users who received a positive result could be routed to a telehealth provider — but the design needed to:

  • Surface the right care options based on the specific condition diagnosed
  • Make the telehealth consultation feel accessible and low-friction, not clinical or intimidating
  • Clearly communicate what the visit would cover, what to expect, and what it would cost

I worked closely with the clinical team to categorize care types and develop a condition classification system that could scale as Cue added new tests to the platform.

Care categorization and classification system

Treatment User Flow

User flow — treatment and care pathway

Care Flow

User flow — care ingress and consultation

High Fidelity Care Designs

Care screen high fidelity Care high fidelity designs

Extended App Screens

App screen App screen
4.

Prescription: Rx Checkout & Delivery

Prescription Delivery

For users whose telehealth consultation resulted in a prescription, Cue offered same-day or next-day delivery through a pharmacy partner network. Designing the Rx checkout flow required close attention to:

  • Regulatory constraints — Prescription fulfillment flows must meet pharmacy compliance requirements; language, consent, and identity verification all required legal review
  • Delivery expectation setting — Users unfamiliar with same-day prescription delivery needed clear communication about timing, cost, and what to expect
  • Error handling — Insurance failure states, out-of-stock scenarios, and delivery zone exclusions all required specific design treatment
  • End-to-end continuity — The Rx flow needed to feel like a natural continuation of the care visit, not a jarring handoff to a new product
User flow — prescription checkout and delivery
Conclusion:

Health, End to End

The Cue Health platform expansion required navigating a tension that doesn't exist in most product design work: the stakes of clinical accuracy and regulatory compliance alongside the equally real need to create an experience that didn't feel clinical, heavy, or anxiety-inducing for people already dealing with a health concern.

The expansion from a COVID testing tool to a full health platform demonstrated that design continuity matters at every scale. Users who trusted Cue for testing were willing to follow it into care and prescription — but only if the transition felt seamless and the new surfaces felt worthy of that trust.

The work across diagnostics, care, and prescription fulfillment gave me experience designing in a domain where the stakes of every micro-interaction — an ambiguous label, a confusing button state, a missing error message — are meaningfully higher than in consumer software.

← Toyota Owners All Case Studies →