Smart Digital Experiences
The Project
Simplifying the way patients find and book healthcare.
Healthcare is often organized around clinics and internal processes rather than around what patients actually need to get done. Finding the right specialist, comparing options, checking availability, and booking an appointment can mean switching between several websites, phone calls, and disconnected systems — often while the patient is stressed, in pain, or simply short on time.
LumaCare brings the most essential healthcare tasks into a single mobile experience. This case study focuses on the core journey of discovering a doctor and booking an appointment, and documents the UX thinking behind it — from problem definition to final interface.
Industry
Healthcare
Language
English
year
2026
Live
What I Did
✦Product thinking & problem definition✦UX research & competitive analysis✦User flows & information architecture✦Wireframing & interaction design✦UI design & design system✦UX iteration & design critique
The Work
Designing a Clearer Path to Care
The Problem
Healthcare isn't hard because of medicine. It's hard because of the experience around it.
Finding the right doctor rarely feels simple. Patients often move between several disconnected tools and steps just to get one appointment booked — searching for a specialist on one website, calling a clinic to check availability, comparing doctors manually with no clear criteria, and later tracking down reports and prescriptions through completely separate channels.
This fragmentation adds friction to something that's already stressful. And healthcare users are rarely in an ideal state to deal with friction — they may be in pain, worried, unfamiliar with medical terms, or simply pressed for time.
Here's what that looks like in practice — a single, common path a patient might take today.
How might we help patients find the right doctor and book an appointment with less effort and uncertainty?
Deliverables
Logo — all formats (PNG, SVG)
Color palette + typography
Design system documentation
UI screens — 11 core flow screens
User flow & IA diagrams
The Approach
Instead of listing every possible feature, the design focused on four decisions that directly respond to the problems above:
Visual Identity
LumaCare's visual language was built around trust and calm — a deep navy accent paired with soft neutral surfaces, generous spacing, and a rounded, approachable geometry. The palette and logo needed to feel credible enough for a healthcare product while staying warm rather than clinical.
Information Architecture
How LumaCare Is Organized
The product is organized around 5 primary areas accessible from the bottom navigation — Home, Appointments, Reports, Notifications, and Profile — with Doctor Search and Pharmacy reached contextually from Home. This keeps the main navigation short and predictable, while still giving quick access to the two most time-sensitive tasks.
The Primary Flow
The Core Task: Finding and Booking a Doctor
The main flow we designed end-to-end covers the task most patients need to complete: going from "I need a doctor" to a confirmed appointment.
UX Problems & Iterations
What Changed Along the Way
The main flow we designed end-to-end covers the task most patients need to complete: going from "I need a doctor" to a confirmed appointment.
Early versions revealed a few recurring issues, fixed through iteration rather than assumed correct on the first pass.
Example 1 — Doctor cards: Problem: Initial cards tried to show too much information, making results hard to scan. Iteration: Reduced to key decision criteria only (photo, rating, price, next availability); secondary details moved to the profile.
Example 2 — Home screen visual hierarchy: Problem: An early version treated all sections with equal visual weight, so nothing stood out as "what matters right now." Iteration: The upcoming appointment became the single largest, most prominent element, with everything else secondary.
The Final Product
The 11 screens below represent one continuous flow, but they group naturally into four stages of the user's actual task: finding a doctor worth considering (Discovery), narrowing that list down to one (Decision), completing the appointment details (Booking), and getting a clear confirmation that it's done (Confirmation). This structure — not just screen count — is what the earlier flow and iteration decisions were built around.
Handoff & Specifications
Design work isn't finished when the screens look right — it's finished when a developer can build them without guessing. Alongside the final screens, LumaCare's handoff package includes:
Spacing & sizing specs — exact padding, margins, and element dimensions annotated directly on key screens
Component states — default, pressed, disabled, and error states for buttons, chips, and input fields
Content rules — max character limits, truncation behavior for long doctor names or clinic addresses
Interaction notes — what happens on tap, on validation error, and expected transition timing
Accessibility requirements — touch target minimums, contrast ratios, and focus order, tied directly to the design system's accessibility guidelines
Below is a redline example from the Doctor Profile screen, showing the level of detail carried into developer handoff.
Reflection
This project reinforced a few things: reducing information often improves decision-making more than adding features does. Healthcare interfaces need extra clarity because users are rarely in a calm, attentive state. And showing availability and price early removes a major source of friction that's easy to overlook when designing around "features" instead of "tasks."
What I'd test next
Symptom-based search comprehension · doctor comparison usage · filter priorities · booking completion rate · accessibility with less tech-confident users
The Result
One connected path — from first search to a confirmed appointment.
↗
Doctor discovery without switching between apps
↗
Clear comparison before committing to a booking
↗
Availability and price shown from the very first screen
↗
One connected flow
↗
from search to confirmation
Client feedback
“
