Screenshots from the live app.
$inspect doc-appoint --summary
role="Solo full-stack developer"
status="live"
stack=["React.js", "Node.js", "Express.js", "MongoDB", "Tailwind CSS", "JWT"]
✓ build verified · demo online
Doc Appoint — ডাক্তার অ্যাপয়েন্টমেন্ট বুকিং
রোগীরা স্পেশালিস্ট দেখেন ও স্লট বুক করেন — JWT ক্লায়েন্ট ও Express সার্ভার।
Problem
Patients still hunt specialists in chats and walk-ins. I wanted a booking flow they can finish in a few clicks: browse a specialty, pick a doctor, lock a slot.
Stack
React.js and Tailwind CSS on the client. Node.js, Express.js and MongoDB on the server, with JWT for protected bookings.
- Client: doc-appoint-client
- Server: doc-appoint-server
Architecture
React client
│ JWT + JSON over HTTPS
▼
Express REST API
│ booking and user data
▼
MongoDB
The client and API live in separate repositories. The browser sends the token with protected booking requests; the Express layer verifies it before reading or writing appointment data.
What I built
- Specialty grid (cardiology, neurology, pediatrics, and more) so users land on the right doctor list
- JWT-backed booking so slots are not a public POST
- Separate client and server repos so the API can be reused
- Responsive landing and booking UI
Key decisions
- Kept the API separate from the React client so authentication and booking rules stay on the server.
- Used JWT for protected routes instead of trusting client-side state.
- Built specialty-first navigation so a patient reaches relevant doctors with fewer steps.
Challenge and result
The main challenge was connecting the booking UI to protected API routes without exposing authorization decisions in the browser. The result is a deployable client/server flow with public source for both parts. This is a learning project, so no production user or revenue claims are made.
Demo numbers on the live marketing page are placeholder copy for the assignment UI — the work to review is the booking flow and the auth split, not those stats.
