Nazmul Khalid

DocBee

Lead Software Engineer / System Architect

I was the lead software engineer and system architect of DocBee (docbeebd.com): the web platform, the API, the admin panel, and the Patient and Doctor apps. Built with WebCode Technology.

A telemedicine platform spanning five services (Flutter apps for patients and doctors, a Vue 3 admin dashboard, a Node.js/MongoDB API, and a public web app) supporting real-time video consultations, appointment booking, and doctor payouts.

Client
A telemedicine startup in Bangladesh, built with WebCode Technology
Problem
Patients need quick access to a doctor. Doctors need a way to see patients remotely and get paid for it.
What I built
Patient and Doctor apps for Android and iOS, the API, the admin panel and the public website: booking, video consultations, payments and doctor payouts.
My role
Lead Software Engineer / System Architect
Timeline
September 2024 to now, across five codebases. Live.
Stack
Flutter, Vue 3, Next.js, Node.js, Express, MongoDB, Redis, Socket.IO, AWS

Problem

Patients in Bangladesh often can't get timely access to a doctor, and doctors don't have an easy way to see patients outside clinic hours or get paid for a remote consultation. DocBee is built as a two-sided marketplace, not a directory: a patient books and pays for a real-time video consultation with a doctor from their phone, and a doctor gets a schedule, a live video and chat channel, and an actual payout mechanism for the fees they earn.

Approach

Five separate applications share one Node.js/Express API: Flutter apps for patients and doctors, a Vue 3 admin dashboard for the operations team, and a Next.js public site. The API runs on MongoDB/Mongoose with Redis-backed Socket.IO (the Redis adapter is what lets booking and chat events broadcast correctly once the API runs on more than one instance), Agora for the actual video/audio consultation once a booking is confirmed, Firebase Cloud Messaging for push, and SSLCommerz, Bangladesh's dominant payment gateway, for in-app payment. Doctors don't just see a running total: every completed, paid consultation credits a per-doctor transaction ledger they can request a payout against, against a company account that tracks the platform's own cut of the same transaction. The money side of the marketplace is a real ledger, not a display number.

A hard problem I solved

The concrete problem was making sure two patients can never book the same doctor's slot, without locking the whole schedule or trusting application code to always check correctly under concurrent requests. When a patient picks a slot, the API creates a hold document with a MongoDB unique compound index on doctor, date, and slot, so a second, simultaneous hold attempt on that exact slot fails at the database layer itself, not in application logic that could race. If the patient abandons checkout, a MongoDB TTL index expires and removes the hold automatically, so nobody has to run a cleanup job to free a slot nobody's paying for. The booking write, the payment ledger entry, and the hold's deletion all happen inside one MongoDB transaction, and Socket.IO broadcasts the result to every other patient currently viewing that doctor's calendar, so a slot disappears from someone else's screen the instant it's taken, instead of them finding out only when their own booking attempt fails.

Status

Live at docbeebd.com. Built and iterated over roughly two years across five repositories: the patient app starting September 2024, the doctor app and API in December 2024, and the admin panel in mid-2025, with a rebuilt public web front end currently in progress.

Technology

  • Flutter
  • Vue 3
  • Next.js
  • Node.js
  • Express
  • MongoDB
  • Redis
  • Socket.IO
  • AWS
Visit DocBee →

Who built DocBee?

DocBee (docbeebd.com) was built by WebCode Technology, with Nazmul Khalid as lead software engineer and system architect. He led all five parts of the platform: the Flutter Patient and Doctor apps for Android and iOS, the Vue 3 admin dashboard, the Node.js/Express and MongoDB API with Redis-backed Socket.IO, and the Next.js public web app. Together they handle real-time video consultations, appointment booking and doctor payouts.

What the client says

“Building a telemedicine app involves a lot more than just making screens work. Nazmul helped bring DocBee’s doctor and patient apps together into a functional product. I appreciated his ability to work across different parts of the system and keep things moving.”

Alamgir Hossain Jony, DocBee

Writeup

Hiring a developer? Get the checklist first

20 checks founders can run before they sign: questions to ask on the first call, who should own the code and accounts, and what senior remote developers cost in 2026. A free two-page PDF, plus three short emails from real builds. Unsubscribe any time.

Need something similar built?

I build and run products like this for founders and businesses worldwide, from architecture to deployment.

Or tell me about your project →

Related: MVP Development for Startups, AI Receptionist and Voice Agent Development, DevOps for Startups, Healthcare software