Studio
Studio Portfolio Exercise · iOS · Android

CuraCare

End-to-end mobile app design for a patient-doctor matching platform, from design system primitives through to production-ready screens.

Twenty-one CuraCare screens: onboarding, the symptom questionnaire, insurance, doctor matching, booking, payment, and the five-tab app
Role
Solo Designer
Platform
iOS · Android
Type
Portfolio Exercise

The right doctor, for you

Healthcare discovery is historically fragmented, opaque, and stressful. Existing platforms like Doctolib and ZocDoc present dense lists with poor filtering and booking flows that feel clinical and impersonal. CuraCare removes that friction.

The core thesis: surfacing one great doctor is better than twenty mediocre ones. The matching feed uses an AI-assisted relevance model to immediately show patients the right specialist, based on symptoms, location, availability, insurance, and preferences.

Every design decision is anchored to one question: does this reduce the anxiety of finding a doctor, or does it add to it?

Two sides of the same problem

CuraCare is a two-sided platform. The primary design focus is the patient experience, with doctor needs informing profile and availability design.

Built from system primitives

The design system uses a tonal palette model: 5 key hues each expanded to a 13-step tonal scale (tones 0 to 100), then mapped to semantic system roles for light and dark mode. Every token is backed by a Figma variable with text styles bound to typography variables.

Full design system Colours, Typography, Spacing, Shape, Elevation. All tokens with Design and Dev views, on its own page.

Complete screen library

From first-open onboarding through doctor discovery, booking, and a full 5-tab main app, every screen is assembled from the same component library and design token foundation.

Try the live prototype Fully interactive. Splash screen through to main app. Click the phone to open it and run the real flows.

Onboarding & Booking Journey

Main App: 5-tab Interface

After onboarding, users land in a persistent 5-tab shell (Home, Search, Appointments, Requests, and Profile), each built from shared components and live navigation state.

The decisions behind every screen

Five principles govern the design, anchoring decisions when trade-offs arise.

Next case Forkful