Case study · Health product · 2026

A family health app built around three moments that matter

ClientHealthcare providers Year2026 RoleLead UX/UI Designer Team3 designers · 5 days

A patient app that hospitals and clinics can brand as their own, framed and built with AI by three designers in a five-day workshop.

Your guide is Dr. Pilly, Kin’s cartoon health assistant and not a real doctor. He narrates the case study as you scroll.

Try the live demo

Scope of work

Product framingWorkshop facilitationAI-assisted prototypingAR & conversational designAccessibility
Two phones: the Kin home screen switched to Mama, with her next visit and three shortcuts, and the booking step that asks who the visit is for. Two phones: the camera view of a real lift lobby with mint arrows on the floor leading to Lift B, pinned with a label, and a corridor with the café labelled in view. Two phones: Dr. Pilly, the cartoon assistant in a lab coat, asking one safety question about a headache, then calm guidance with two suggested doctors.

Book a visit for yourself or anyone in your family, in three steps.

My role

Lead UX/UI Designer. I ran a five-day workshop with a senior and a junior designer, led the AI work and reviewed everything we shipped.

Scope

A bilingual patient app: 16 flows, with three journeys taken to depth: booking, wayfinding and a health assistant.

Status

A working product prototype, ready to demo to hospitals and clinics.

About this caseShown under a placeholder brand, Kin. Every name, doctor, hospital and figure is fictional.

My role, the team and the scale

Three designers, five days, every decision made together. We built in Figma Make, which turns written briefs into a working app; I wrote the briefs, the refinement prompts and the assistant’s safety rules.

How I led, one exampleOn day two the first build showed the assistant as a real doctor. I paused the build and put the risk to the team, and we agreed three rules together: a danger check first, no doses in chat, and “not a real doctor” on every screen. I turned them into the next prompt and a review checklist, and we checked every assistant screen against it before moving on.

5day workshop
3designers: lead, senior, junior
47screens from a 16-flow brief
2languages, Arabic and English
  1. FrameWho it’s for, and the moments that matter.
  2. Brief16 flows with every edge case, then the first build.
  3. ReviewUsed it as patients would, and read the code.
  4. RefineRounds of fixes, each with a checklist.
  5. FocusThree journeys taken to depth.

Research: what patients already use, and who we designed for

Our research was desk-based, on day one of the workshop: public app listings, the health apps we use ourselves, and Saudi rules for health software. Talking to patients and carers is the next step.

What patients already use

From public store listings and our own use, not a full feature audit
What existsWhat it does wellWhere it stopsWhat we took
Sehhaty, the national health appBooking at national scale, in person and by video, with dependents and children’s vaccinesPublic care. It doesn’t guide you once you’re inside a private hospitalTreat the family as the user
Private hospital group appsBooking, family files, results and insurance approvals in one accountFamily sits in a menu, and help ends at the car park“Who is this for?” as a booking step, and guidance to the clinic door
Telehealth appsA video visit in minutes, medicines deliveredSeparate from the hospital you visit in personVideo visits in the same app as in-person care
Global symptom checkersAn answer for any symptom, any hourLong lists of causes, a frightening tone, no link to local care or 911A danger check first, then a real doctor nearby

The gapNo one covered the whole visit. Booking, the walk inside the building and the worry between visits lived in different apps, or nowhere.

Who we designed for

Four people: the family carer, the older patient, the Arabic-first patient and the midnight searcher.

HypothesesNo patient interviews were part of the workshop, so these are working profiles drawn from the desk research and our own families. Testing would confirm or replace them.

See the four profiles
Hypothesis

The family carer

Wants: to book and drive for parents and children without juggling accounts.

Needs: a “who is this for?” step and everyone’s visits in one place.

Hypothesis

The older patient

Wants: to arrive on time without asking for directions.

Needs: large type, step-free routes and a map that works without the camera.

Hypothesis

The Arabic-first patient

Wants: an app that feels made in Arabic, not translated.

Needs: right-to-left layouts and the medical words people actually say.

Hypothesis

The midnight searcher

Wants: to know if a symptom is serious, without being scared.

Needs: a quick danger check, plain words and one clear next step.

How might we…

  • …let one person book for the whole family without switching accounts?
  • …get a patient from the car park to the clinic door without asking anyone?
  • …answer a worried question at midnight safely, and know when to say “call 911”?
  • …make Arabic feel native from the first screen?

Three moments patients remember

We grouped every flow by when a patient needs it and took one journey from each moment to depth. “Who is this for?” runs through all three.

Before the visit
  • Book an appointment
  • Find a doctor
  • Payments
On the day
  • Find your way inside
  • Video visit
  • Check in
Between visits
  • Ask Dr. Pilly
  • Results
  • Health tracker
Around it all
  • Family
  • Messages
  • Settings

Why these three

  • BookingThe job every app we looked at is built around, and the one carers do most for others.
  • WayfindingThe gap no app covered. Getting lost makes patients late, and late patients cost clinics their slots.
  • The assistantThe riskiest moment, so it needed the most design care.

Try it yourself

The demo is the whole app on sample data. On a computer it opens in a phone frame with a guide beside it; on a phone it fills the screen.

The Kin demo in a browser: a guide to the journeys on the left and the app in a phone frame on the right.

Kin, live demo

  • Switch to Mama and book her a visit.
  • Take Directions and let Dr. Pilly walk you to the clinic.
  • Tell Dr. Pilly about a headache, and answer his question both ways.
Open the live demo

1 · Booking, for anyone in the family

Three steps after choosing a doctor: when, who, pay.

Four phones: a doctor profile with a 4 PM slot selected, the day and time step, the step asking who the visit is for with Hessa, the mother, selected, and the booking confirmation.

2 · Finding the way, with augmented reality

Hold the phone up and the route appears on the real floor, with Dr. Pilly floating a few steps ahead. It works in all three partner buildings, a hospital, a family clinic and a diagnostics lab, and every destination has its own route and arrival, with a floor map that follows you level by level.

In the demoAI-generated photos of the hospital, clinic and lab stand in for the live camera. The product would use AR tracking and indoor positioning.

Three phones showing arrival in augmented reality: the laboratory reception, emergency triage with a red guide line and Dr. Pilly serious, and the pharmacy counter, each marked with a ring on the floor.

3 · Dr. Pilly, an assistant that knows his limits

Between visits, people search symptoms and scare themselves. Dr. Pilly calms, informs and routes them to real care.

Four phones: Dr. Pilly asking whether a headache started suddenly, a get-seen-now card with Call 911 and directions to Emergency, calm guidance with two suggested doctors, and an ibuprofen check against saved medicines.

Giving the assistant a face

A chat window feels cold when you are worried about your mother, so the assistant got a character. His cartoon name makes it obvious he isn’t a person, and he wears Kin’s navy and mint.

Dr. Pilly's seven states: idle, listening, thinking, done, needs attention, loading and offline, with the rule: Dr. Pilly shows what the system is doing, and safety always beats personality.

The rest of the app

Every flow from the brief works in the demo: Nafath sign-in, health tracker, prescriptions, medicine scanner, video visits, AR first aid, family hub, rewards and accessibility settings.

Four phones: the health tracker with a high glucose warning, the family hub, a video visit, and AR first aid guiding hands for CPR.

Where we overruled the AI

The first build looked helpful and would have been unsafe. These were the calls that mattered most.

Before and after. Left, the first AI build, recreated: an assistant named as a consultant at a hospital promises a diagnosis, lists causes up to a brain tumour, and gives a child’s dose. Right, what we shipped: Dr. Pilly, labelled not a real doctor, asks one safety question first.
What the AI produced, and what we changed
The AI producedWhy it mattersWhat we did
An assistant presented as a real doctor from a real hospitalPeople trust a doctor’s titleAn obvious cartoon, “not a real doctor” on every screen
Possible causes before any check for dangerA list can delay someone who needs help nowOne safety question first, with a route to 911
Children’s doses by weight, in chatA child’s dose belongs to a pharmacistRemoved. Points to the label and the pharmacist
Health figures with no sourceUnsourced figures misleadRemoved every figure we couldn’t source
Boxes keyboards can’t reach, 2.5:1 grey textFails WCAG AA, and many patients are olderReal controls, AA contrast throughout

Design decisions

The family is the user

“Who is this for?” is a booking step and a home-screen switch, not a buried setting.

Co-pay up front

Fee, VAT and what insurance covers, in riyals, before the confirm button.

Arrows on the real floor

Find the floor first, one arrow style everywhere, labels pinned to real places.

The map isn’t a fallback

A floor map and step-free routes for anyone who won’t or can’t use the camera.

Safety before personality

A danger check before any advice, and no jokes in an emergency.

Journeys hand over

A booking leads to directions, and Dr. Pilly leads to a doctor.

Who pays, and what could go wrong

Kin is sold to hospitals and clinics, who brand it as their own. Here is why a provider would pay, and the risks we’d raise before anyone signs.

Why a provider would pay

  • Fewer empty slotsPatients who arrive on time, and reminders that cut no-shows.
  • A lighter front deskBooking and “where is the clinic?” move from the phone line and reception to the app.
  • Whole familiesOne carer brings a household’s visits to the same provider.
  • Their brand, ready madeA tested patient app in their colours, instead of building one from scratch.

How we’d sell itAn annual licence per facility, priced by size, with setup and AR mapping charged per building. That keeps the first contract small and lets AR grow with proof.

Risks and how we’d respond

The big three: the assistant may count as medical software, health data falls under the PDPL, and AR costs money per building.

See all six risks and our responses
Regulation notes are our reading of public guidance, to confirm with the provider’s legal team
RiskWhy it mattersHow we’d respond
The assistant counts as medical softwareSFDA can regulate software that assesses symptoms as a medical deviceKeep it to triage and routing, never diagnosis. Confirm its class with SFDA early
Health data and privacyThe PDPL sets rules on consent, where data is stored and transfers abroadData kept in the Kingdom, consent per family member, guardians only for dependents
Liability for adviceOne wrong answer could harm someoneClinical sign-off on every answer, 911 always one tap away, no doses in chat
Links to national systemsBookings, sick leave and insurance approvals run through Ministry and insurer systemsStart with the provider’s own booking system, then add national links one by one
AR costs per buildingIndoor positioning needs a mapped building and sometimes beaconsLaunch with the floor map everywhere, then add AR one building at a time, busiest first
A cartoon in a hospitalA mascot can feel unserious to some patientsTest with carers and older patients. Dr. Pilly turns serious in any emergency

How we’d measure success

The product isn’t live yet, so there are no results to report. These are the measures and starting targets we’d agree with a launching provider.

Proposed success measures
GoalWhat we’d measureBaselineStarting target
Easy bookingBookings completed after opening a doctor’s profileThe provider’s current appA fifth higher in 90 days
Care for the familyShare of visits booked for someone elseNone yet, a new measureLearn for 90 days, then set
On time, without helpLate arrivals and “where is the clinic?” questions at receptionA one-week reception tally before launchA third fewer in AR buildings
Safe guidanceRed-flag chats sent to emergency, and unsafe answers in clinical reviewA scripted set of test casesEvery red flag routed, zero unsafe answers

What we’d test first

  • Booking for a parentCan a carer book for their mother without help? Moderated sessions with five to eight carers.
  • The danger checkDo people answer the safety question, or skip past it? Scripted scenarios, reviewed by a clinician.
  • AR in a real corridorDo older patients hold the phone up, or prefer the map? On site with one partner building.

Outcome

In five days, three designers turned a brief into a working, bilingual product a provider can see in one meeting.

What it provesAI can get a small team to a working product in a week, but only with someone setting the rules and reviewing like an engineer. Our most important work was what we removed.

Next comes testing with patients and carers, clinical sign-off for every assistant answer, then hospital integrations and indoor positioning per building.

More Projects

Like what you see?Let's discuss your next project.

Chat on WhatsApp (opens in a new tab)