Skip to content
All guides

· 8 min read

How to build a doctor appointment app: lessons from DocRadar

Doctor appointment app development, from a Flutter app we built: real-time availability, doctors nearby on a map, in-app payments, roles and store review.

Blueprint-style cover reading: Building a doctor appointment app

To build a doctor appointment app, start with the three questions every patient brings to it: which doctors are available, which of them are near me, and how do I book and pay. A first version that answers those quickly, on both iPhone and Android, with secure sign-in and a separate role for each kind of user, is a real product. Video consultations, medical records and insurance claims can wait. We learned this on DocRadar, a doctor booking app we built in Flutter, and this post turns that build into lessons you can use on your own.

Some context first. DocRadar connects patients with doctors, in cities and in underserved areas alike. One Flutter codebase serves iOS and Android, on a Node.js, Express and MySQL backend that runs on AWS.

What a first version needs, and what can wait

Build in the first versionLeave for later
Sign-up and login, with a role for each kind of userVideo consultations
Doctors listed by specialty, with ratings and reviewsMedical records, test results and prescriptions
A map of doctors and clinics near the patientInsurance claims
A clinic page with address, distance, hours and a booking buttonFamily accounts and booking for others
Real-time availability and bookingChat between patient and doctor
Payment inside the appLoyalty schemes and discounts
A way for your own team to manage doctors and clinicsDetailed reports for clinic chains

Everything on the right is useful, but none of it decides whether a patient can find a doctor and get an appointment. Our guide on how to scope an MVP covers how to make these cuts without losing the core of the product.

Lesson 1: answer the patient's three questions on the first screens

A patient opening a doctor appointment app is often worried, in pain or short of time. They are not browsing. They want an answer.

DocRadar's screens follow that order. After logging in, a patient browses top specialists by field, and a map shows the doctors and facilities near them. A clinic page gives the address, distance, opening hours and reviews, with a button to book. Payment follows inside the app.

Practical points from this:

  • Put search by specialty and location on the first screen. "A skin doctor near me" is a typical way to put it.
  • Show availability before the patient taps through. A doctor with no free slot this week should not look the same as one with a slot this afternoon.
  • Count the taps from opening the app to a confirmed booking. Then remove some.

Lesson 2: availability is the hard part

Showing doctors is easy. Showing which of them can see you, and when, is where most of the work in doctor appointment app development sits. DocRadar shows real-time availability, and that depends on decisions that have little to do with screens:

  • Who keeps the calendar up to date. A doctor, a receptionist or a clinic's existing system. If nobody owns it, the app shows slots that are not really free, and patients stop trusting it after one wasted trip.
  • How a slot is defined. Fixed lengths per doctor, different lengths per type of visit, breaks, holidays and days at a second clinic all have to be modelled.
  • What happens when two people tap the same slot. The database has to accept the first booking and refuse the second, every time. A relational database such as MySQL, which DocRadar uses, handles this well with transactions.
  • Cancellations and no-shows. Decide early what a patient can cancel, until when, and what happens to any payment.

Write these rules down in the blueprint week. They shape the database and the doctor's side of the product far more than any visual choice.

Lesson 3: location does a lot of the work

Patients usually choose a doctor partly by distance. DocRadar uses Google Maps geolocation to show available doctors and facilities near the patient in real time, and each clinic page shows how far away it is.

Three things we would tell anyone adding a map to a booking app:

  • Ask for location at the moment it helps. Ask when the patient opens the map, not on the welcome screen, and explain why in one line.
  • Work without it. Some people say no. Let them choose a city or an area instead, so a refusal does not end the journey.
  • Budget for the maps bill. Google Maps Platform charges by usage once you pass its free allowances. Check the Google Maps Platform pricing for the maps, places and directions calls you plan to make, and set usage alerts before launch.

DocRadar was built for underserved areas as well as cities. Outside big cities the nearest doctor may be far away and the signal weak, so keep screens light and put distance and opening hours where they are seen first.

Lesson 4: help patients choose with information they trust

A list of names is not enough to pick a doctor. DocRadar shows specialists by field with ratings and reviews, and the clinic page adds the address, distance, opening hours and reviews.

Reviews in healthcare need more care than restaurant reviews. Decide who can leave one (only patients with a completed appointment is a sensible rule), what your team does with a review that names a medical complaint, and how a doctor can respond. Then give your team an admin screen to act on it.

Lesson 5: payments inside the app, and the store rules around them

DocRadar takes payment inside the app through Stripe, with a choice of payment methods. Taking payment at booking tends to reduce no-shows and gives the clinic a record, but it brings decisions with it: refunds on cancellation, partial payments, and what the clinic receives after fees.

Will Apple and Google insist on their own in-app purchase systems? For appointments, generally not. Apple's App Review Guidelines say in section 3.1.3(d) that apps selling real-time person-to-person services, with medical consultations named as an example, may use other payment methods, and section 3.1.3(e) says services consumed outside the app must use methods other than in-app purchase. Google Play's payments policy draws a similar line for physical services. Read the current wording for your case before you build: a group class or a paid subscription can fall under different rules.

Lesson 6: one app, several kinds of user

A doctor appointment app is a two-sided market. Patients want appointments, doctors and clinics want their slots filled, and your own team needs to add, check and remove doctors.

DocRadar has secure authentication and role-based access, so each kind of user only sees and does what their role allows. Three practical rules:

  • Check roles on the server. Hiding a button is not security. The API should refuse any action the role does not allow.
  • Verify doctors before they appear. Decide what you check, such as registration with the local medical council, and who checks it. A person reviewing documents in an admin panel is a fine start.
  • Plan account deletion from the start. Apple's guidelines require apps that let people create an account to let them delete it from inside the app.

If this sounds like a marketplace, it is one. Our post on building a rental marketplace app covers the same two-sided problems in a different market.

Lesson 7: treat health data as sensitive from day one

Even a booking app holds sensitive information. An appointment with a psychiatrist or an oncologist says something about a person's health.

  • Collect the least you need. A first version usually needs a name, a phone number or email, and the appointment. It does not need a medical history.
  • Keep files private. DocRadar keeps files in Amazon S3. Storage like this should be private by default, with short-lived links for anyone allowed to see a file.
  • Write a clear privacy policy. Apple requires one for every app, and its guidelines set extra rules for health and medical data, such as not using it for advertising.
  • Check the law where your patients are. Health data rules differ by country. If you serve patients in the US, Europe or the UK, get advice on the rules there before launch, not after.

Lesson 8: one codebase for both stores

Patients use whatever phone they have, so a doctor app usually needs iPhone and Android from day one. We built DocRadar in Flutter, so one Dart codebase produces both apps. Flutter has mature packages for maps and payments, the two main integrations in an app like this.

The backend matters as much as the app. DocRadar runs on Node.js and Express with MySQL, on AWS EC2, with S3 for files. If you are choosing between frameworks, our comparison of React Native vs Flutter for startups sets out when each one fits.

Lesson 9: leave room for store review

Apple's guidelines say medical apps that could give inaccurate information, or be used to diagnose or treat patients, may get greater scrutiny. A booking app that gives no medical advice is a simpler case, but reviewers still test sign-up, booking and payment. Give them a demo account with test bookings, and leave time in the plan for a second round. Our app store launch checklist lists everything to have ready.

How to build a doctor appointment app: a short checklist

  1. Put specialty, location and availability on the first screens.
  2. Decide who keeps each doctor's calendar up to date.
  3. Make the database refuse a double booking.
  4. Ask for location when it helps, and work without it.
  5. Decide refunds, cancellations and no-shows before building payments.
  6. Check roles on the server and verify doctors before they appear.
  7. Collect the least health data you can, and keep files private.
  8. Build iPhone and Android together, and leave time for review.

Booking apps with location and payments are the kind of product on our mobile app development page, and DocRadar is the example on our Flutter app development page. If you are planning a healthcare app of your own, our MVP development process starts with a blueprint week and a fixed price, or you can tell us what you are building and we will come back with a plan.

  • Healthcare
  • Case study
  • Mobile apps

Building a first version of your product?

We scope it in a week and launch it in 8–12, for a fixed price. Tell us what you want to build.