Lybrate's patients book a doctor, consult by text or video and get lab tests at home, in one app.
Lybrate, one of India's largest doctor-patient platforms, wanted patients to reach a doctor of any specialty and book a consultation in real time, and to keep getting the features they asked for, quickly.
What changed
What stood in the way.
- Use of the platform was growing fast, but Lybrate could not ship user feedback and new features as quickly as its competition required.
- The team struggled to keep the existing product running while moving it forward.
- The apps ran on an obsolete stack with unoptimised code, which slowed them down and piled up technical debt.
- Both apps needed text consultation, telehealth and telemedicine modules and patient forums.
- 40%less go-to-market time (as reported)
- 5M+app downloads (as reported)
- 150,000+medical experts registered (as reported)
What we built.
- Took over two integrated web and mobile apps, one for doctors and one for patients, on Android and iOS, built in Java, Swift and SQLite.
- Moved the whole codebase to the Amazon cloud on a multi-tier architecture for speed and scale.
- Text messaging on Socket.IO, so many conversations run at once and arrive quickly.
- An Add Prescription feature that syncs the doctor's and patient's apps, with each medicine and its dosage.
- Automatic prescription reminders, and an appointment module for booking consultation slots that manages the doctor's slots and cuts the patient's wait.
- Links to certified diagnostic labs for tests at the patient's door and reports shared online with the doctor.
- On-demand video consultation, a telehealth module for remote monitoring and health advice, and a patient forum where doctors share articles.
- Agile delivery with continuous integration and testing, releasing each module as soon as it was ready.
- Java
- Swift
- SQLite
- Socket.IO
- Amazon cloud
- Android and iOS
What this work shows about us.
Booking, the consultation by text or video, the prescription, the reminder and the lab test are one journey, built across the doctor's app and the patient's app.
We built for the doctors who give care and the patients who seek it, with each action in one app showing up in the other.
Releasing module by module cut go-to-market time 40% (as reported) while the platform kept serving more than 10 million visitors.
Want to build similar doctor and patient telehealth apps? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.
Start your plan ↗If we built it today, with AI.
This work came before today's AI. If Lybrate asked us now, this is what we would add, step by step.
An agent would ask a patient what is wrong in their own words, suggest the right specialty and offer the earliest slot. The patient chooses, and the doctor decides on care.
An agent would draft the consultation note and prescription from a text consultation, for the doctor to check, change and sign.
An agent would book the home lab visit the doctor ordered, chase the lab if the report is late and send it to the doctor marked as new.
An agent would follow up each prescription reminder, ask whether the patient took the medicine and tell the doctor when doses are being missed.
Where this work fits.
- Hospitals & clinicsYour hospital is meant to deliver care without making patients wait.
- Clinic & practice managementPatients book in a message and wait at home, not in the waiting room.
- A European healthcare companyUsers get a diet plan built around their health, their allergies and the food sold where they live.
- A US telehealth weight-loss providerThe provider's patients book a consult, log meals and weight each day, and know when to reorder medication, from one web app.
Facts and figures from the project records; nothing added.
Want this for your business?
Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.
Send us a note instead
An AI agent. This prototype uses prepared answers and sends nothing.
We use essential cookies to run this site. With your consent we also use analytics cookies to see which pages help. Privacy policy