Overview

Doctor Booking is a healthcare-oriented web app that demonstrates booking workflows and role-aware product thinking.

My Role

I contributed to building the application experience and connecting UI flows with MERN-style application logic.

Problem

A booking platform must make it easy for users to find the right provider and move through an appointment flow without friction.

Solution

Positioned the project around appointment flow rather than cart/checkout language.

Target Users

  • Patients
  • Doctors or clinics

Workflow

Product flow from interface to deployment

01

UI

02

API

03

Auth

04

Data

05

Deploy

Key Features

  • Doctor/profile browsing
  • Appointment-focused workflow
  • Authentication-aware user experience

Frontend Implementation

  • Built responsive React screens for browsing and appointment interactions.
  • Used form and state patterns suitable for booking workflows.

Backend / API Implementation

  • Node/Express and MongoDB support authentication and appointment workflows.

Database Design

  • Application data centers on users, doctors, and appointments.

Authentication and Security

  • JWT-based authentication protects user account flows.

API Overview

  • Application flows connect authentication, doctor discovery, appointments, and user accounts.

Architecture Decisions

  • Booking apps benefit from clear separation between discovery, booking, and account flows.
  • The MERN stack supports fast iteration across UI, API, and data.

Challenges

  • Avoiding generic e-commerce patterns in a healthcare booking UX.
  • Keeping appointment interactions clear on mobile.

Solutions

  • Positioned the project around appointment flow rather than cart/checkout language.
  • Used healthcare-specific language and interactions throughout the booking experience.

Deployment Notes

  • Public demo is available on Vercel.

Database Schema Notes

User

profileauthappointments

Doctor

specialtyavailabilityprofile

Appointment

patientdoctorstatus
  • Schema cards describe the core user, doctor, and appointment entities.
User -> AppointmentDoctor -> AppointmentAppointment -> Status

What This Project Proves

Booking workflow thinking
Full-stack product structure
Auth-aware UI
Domain-specific product copy