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
- Admins if supported
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
- Dashboard or management screens where supported
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 backend and MongoDB are listed in the project stack.
- Add exact endpoint and role details after reviewing the backend repository.
Database Design
- Expected data includes users, doctors, and appointments.
- Add real schema details when confirmed.
Authentication and Security
- JWT is listed in the project stack.
- Add details about roles and token handling only after verifying them.
API Overview
- Expected API groups include auth, doctors, appointments, and users.
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.
- Kept the case study honest where backend details still need repository proof.
Deployment Notes
- Public demo is available on Vercel.
Database Schema Notes
User
profileauthappointments
Doctor
specialtyavailabilityprofile
Appointment
patientdoctorstatus
- Schema cards describe the booking-domain entities already supported by the case study copy.
- Detailed backend model links should be added after repository verification.
User -> AppointmentDoctor -> AppointmentAppointment -> Status
Screenshots
Project Screenshot
What This Project Proves
Booking workflow thinking
Full-stack product structure
Auth-aware UI
Domain-specific product copy