Case Study
How this project was designed and delivered
Overview
AllDayDr is a telehealth platform that connects patients with certified medical practitioners through secure video consultations. It aims to make primary care more accessible by allowing patients to book appointments, speak to a doctor, and receive prescriptions without needing to visit a clinic in person.
Problem
Patients often face long wait times, limited appointment slots, and geographical barriers when trying to see a doctor. On the provider side, clinics needed a compliant, reliable way to offer remote consultations, manage appointments, and handle medical records without stitching together multiple tools.
My Role
I worked as a frontend engineer across the patient-facing and clinician-facing interfaces, helping to implement booking flows, consultation rooms, and medical record views. I collaborated closely with backend engineers and compliance stakeholders to ensure that the UI respected privacy constraints and provided a safe, predictable experience for both patients and doctors.
Solution
Using React and AngularJS for different parts of the product, together with WebRTC for real-time video, I helped build flows for account creation, symptom collection, appointment scheduling, and joining a consultation room. I implemented UI components for video calls, chat, and prescription summaries, and worked on state management patterns that kept the experience resilient to network hiccups. On the infrastructure side, the team leveraged AWS services to support secure media streaming and storage.
Outcome
AllDayDr provided patients with a convenient, trustworthy way to access GPs and specialists remotely, while giving clinics a dedicated platform for managing remote care. The modular frontend architecture made it easier to introduce new visit types and integrate additional services (such as referrals and follow-up reminders) without destabilizing the core consultation flow.
This write-up focuses on the product problem, my role, and the key architectural decisions behind the implementation, highlighting how design, engineering and UX came together.
It is intentionally high level and technology-agnostic so it can be read easily by both engineers and non-technical stakeholders.