Healthfy Care
Book and attend a doctor consultation in five taps — without knowing which specialist you need.
An iOS-first consultation product, extended to Android and web. Describe a symptom in your own words, get matched to a credible doctor, take the earliest slot, and meet them over video — with the fee and the cancellation rule visible before you pay.
3 months
9 (2 designers · 7 engineers)
iOS · Android · Web
Clickable hi-fi prototype
Healthfy Care
What's bothering you today?
Say it in your own words — we'll find the right doctor.
"Fever since two nights, headache and no appetite."
Common right now
Triage says: General Physician
Not an emergency. Video consult is enough.
Ranked by symptom fit first, then availability — the reason is printed on every card.
Reason for visit
Fever 2 nights, headache, low appetite. No travel history.
Prescription saved to Records
Paracetamol 650mg · after meals · 3 days. Follow-up free for 48 hours.
One design system, three surfaces: iOS keeps a tab bar and soft cards, Android uses Material shapes and caps, web opens the flow out into a two-pane booking desk.
The design process
Three months, 2 designers and 7 engineers. Research to a tested, clickable prototype in seven steps.
Research
9 interviews (patients, 2 caregivers, 3 doctors), a competitive teardown of 5 consultation apps and a diary study of 6 real booking attempts. The recurring failure: people were asked to choose a specialty before they could name their problem.
Define
One problem statement: 'A worried person needs to reach a credible doctor fast, without knowing which kind of doctor they need.' Success = time-to-confirmed-booking under 3 minutes with no help.
Information architecture
Five destinations only — Book, Visits, Records, Prescriptions, Family. Booking became one linear stack instead of a browsable directory, so nothing competes with the primary task.
Ideate
Three concepts tested on paper: a specialty directory, a chat-style triage bot, and symptom-first matching. Symptom-first won on speed and confidence; the bot felt slow and the directory reproduced the original problem.
Scratch & wireframes
Pencil scratches settled the screen order in a day; grey-box wireframes fixed slot-grid density, thumb-reach for the primary button and where cost is disclosed.
High-fidelity prototype
A clickable iOS prototype of the prioritised flow — intake, match, slot, review & pay, consult room — with an Android variant using Material shapes and a web two-pane booking desk.
Test
Two moderated rounds with 6 participants each. Round one exposed hidden fees and an unclear cancellation rule; round two, after moving both onto the review screen, ran 6/6 unaided.
Information architecture
Book
- Symptom intake
- Matched doctors
- Slot picker
- Review & pay
Visits
- Upcoming
- Join room
- Reschedule
- Past consults
Records
- Prescriptions
- Lab reports
- Doctor notes
- Shared files
Family
- Profiles
- Book for a parent
- Consent
- Shared history
Prioritised user flow
- 1
Describe the symptom
Free text or voice; triage maps it to a specialty and urgency.
- 2
See matched doctors
Ranked by fit, each card stating why it was suggested.
- 3
Take the earliest slot
Pre-selected soonest time; the calendar is an override.
- 4
Review and pay once
Fee, mode and free-cancellation window on one screen.
- 5
Meet and get after-care
Video room keeps the reason on screen; prescription saves to Records.
What makes the booking innovative
Six decisions that turn a directory into a two-minute path to care.
Symptom-first, voice-friendly intake
Type or speak in plain language or Hindi. Triage maps it to a specialty and an urgency level, so nobody has to self-diagnose to get started.
Explained matching
Every doctor card states why it ranked — symptom fit, language, next free time — instead of a bare star rating.
Earliest slot pre-selected
The soonest slot is chosen for you; the calendar is an override, not a task. It removed the longest pause in the flow.
Cost and cancellation up front
Fee, total and the free-cancellation deadline sit on the review screen before payment — the change that cut payment drop-off.
Context-carrying consult room
The reason for the visit stays on screen during the call, so the first 30 seconds aren't spent re-explaining.
After-care that closes the loop
Prescription saves to Records automatically and chat follow-up stays free for 48 hours.
From challenge to outcome
The Problem
What We Learned
The Strategy
How It Was Built
Accessibility
The Impact
What I Carry Forward
Behind the work
My scope, the guardrails I worked inside, what the research changed, and how the work travelled from sketch to production.
My role & scope
Design lead in a nine-person team — 2 designers and 7 engineers — over three months: research, IA, flows, the iOS-first design system, Android and web adaptations, the clickable prototype and both rounds of usability testing.
Constraints & guardrails
- Three months with 7 engineers building in parallel — the prototype had to double as the build spec.
- iOS first, but Android and web could not be visual afterthoughts.
- Doctor supply was thin at launch; the flow had to stay credible with few slots.
- Medical claims and triage wording reviewed by a practising physician.
What research changed
- Participants could not name a specialty for their own symptoms in 7 of 9 interviews.
- The longest pause in the diary study was the calendar screen, not payment.
- Unexplained rankings read as advertising; a one-line reason restored trust instantly.
The pivot
The first concept was a chat-based triage bot. It tested as slow and evasive — people wanted a list of doctors, not a conversation — so triage was moved behind a single intake field and the results screen became the moment of truth.
UX metric → business impact
Pencil scratches of the five-screen stack and card sorting of the five destinations.
Grey-box wireframes for slot density, thumb reach and cost disclosure, tested on paper.
Clickable iOS prototype plus Android and web variants — the deliverable engineering built from.
Retrospective
I would run the pricing disclosure test in week two rather than week eight; it was the single highest-value change and we found it late.
Remove the decision the user cannot make. Naming the symptom, not the specialty, is what made this fast.
“I didn't have to know what kind of doctor I needed. I just said what was wrong and it found someone free this afternoon.”