Brand blue
every primary action, every selected state, and the mark
#4761BCUI/UX Design · Product Design
Doctor booking that makes healthcare feel close — search, profiles, reminders.
Booking a doctor is a high-stakes task performed by someone who feels unwell. Doctify is designed for that person: fewer decisions, clearer profiles, and a reminder that arrives before they need it.
01 The brief
Doctify had to make finding and booking a doctor simple enough to do while feeling unwell.
The objective was one interface that carries the entire appointment: the search, the choice, the booking, and the reminder afterwards.
Doctify is a doctor-appointment booking app. My job was to design an interface that keeps the whole booking intuitive: explore a network of healthcare professionals, filter down to the right specialist, and make the appointment with confidence.
The point of all of it was access. Arranging healthcare is the least convenient thing most people have to do, and the interface is where that either gets better or gets worse. Five things had to be true before it could get better.
Select an available date and time, review the choice, confirm — in that order, with nothing in between.
Find doctors by specialization, location, availability and the other criteria that actually narrow a search.
Qualifications, experience, patient reviews and availability, organised so the choice is easy to make.
Save favourite doctors, set preferences, leave a review — the platform learns who it belongs to.
A notification system that keeps people informed about what is coming, and keeps no-shows down.
02 Research
User interviews, surveys and usability testing put patients on one side of the appointment and healthcare providers on the other.
Patients told me booking was convoluted. Providers told me they had nowhere to prove they were worth booking.
The research shaped the interface and the product strategy together. Patients were frustrated by convoluted booking processes, and just as frustrated by how hard it was to find a specialist for their specific requirement. That is what pushed the design toward a system where you pick an available date and time, review the choice, and confirm — a sequence short enough to finish while unwell.
The other half came from the healthcare providers. They needed a platform where their qualifications and experience could actually be seen. So the doctor profile stopped being a row in a list and became a screen of its own: qualifications, experience, patient reviews and availability, organised so they can actually be read, which turned out to serve the patient's confidence as much as the provider's case.
Both findings are the same finding from two directions: the information existed, and no interface had bothered to organise it.
A booking app only looks like a form. It is really the ten seconds in which somebody decides to trust a stranger with their health.
03 The design
The flow decided what the app was, the sketch what the screens were, and the system what all of it looked like.
information architecture + primary flow
Onboarding sign up · sign in · forgot password
Five destinations on the bottom bar and nothing hidden behind a menu. Search sits on the home screen rather than inside one of the five, because a person who already knows the name of their doctor should not have to guess which tab that lives under. Everything that happens after a booking — upcoming, completed, cancelled — lives in one place, since the appointment, not the doctor, is what brings people back.
the Doctify colour system
every primary action, every selected state, and the mark
#4761BCheld back for one moment: the tick that says it is confirmed
#B9C902type — the only near-black in the app
#1D1617the calendar field and the card a doctor sits on
#DADFF2the quiet surface, where blue would be too clinical
#FFF5E9the field everything else is measured against
#FFFFFFSoothing blues and clean whites are the colours people already associate with medicine, so I started there and paired them with a clear, contemporary typeface so the whole app reads as one thing. In healthcare that consistency is not a style preference: it is what keeps the app reassuring to somebody using it on a bad day.
04 Final screens
Ten screens carry all five: onboarding, home, booking, history, profile.
All five objectives from the brief land on one of these screens.
The doctors list leads with the specialty filter, because finding the right specialist was the harder half of the problem. The profile gives qualifications, experience, reviews and working hours a full screen and puts one action at the bottom of it. Booking is a calendar, a row of hour chips and a Next — pick, review, confirm.
Then the app takes on its second job: holding on to the appointment. Upcoming, completed and cancelled sit behind one control, each card carrying the two things people actually want from it, and the reminder that prevents a no-show turns out to be a single switch in the profile.
05 Testing
Find a specific doctor, book an appointment, move around the app, then tell me what got in the way.
The tasks were deliberately ordinary: find a doctor, book them, and get back out.
Participants worked through finding a specific doctor, booking an appointment and navigating the app's features. They appreciated the search filters — specialties, locations, availability — and then asked for more of them: sorting by patient reviews, filtering by insurance coverage. I expanded the filter options rather than defending the set I already had.
The other note was about the very beginning. Registration had to be more straightforward, so I streamlined the flow and added social sign-in alongside email. The sessions that followed bore that out.
Testing didn't ask me to redesign anything. It asked me to add options in one place and take steps out of the other.
06 Reflection
In healthcare the layout is rarely the hard part. Deciding how much to say is.
Every hard decision on Doctify was a version of the same one. The essential medical information had to fit without overwhelming the interface, and complex healthcare terms had to survive translation into plain language without losing accuracy. One booking flow had to stay simple across specialties that do not work the same way. And all of it sits inside healthcare data-privacy regulation — HIPAA and the rest — without turning the app into a legal document.
What I take from it is that in healthcare, simplifying a process and earning trust are the same job, and that testing settles the arguments, not taste. What comes next is the same list I would give anyone: keep refining the interface, strengthen the privacy measures, widen the accessibility features, so the app stays easy to open when somebody needs care.
An app people open when they feel unwell has to be legible at their worst, not at my best.