One cross platform app
A single React Native codebase served iOS and Android, so every fix and feature reached all patients at the same moment.
Loading…
Loading…
Healthcare
A UAE telehealth provider
A UAE telehealth provider came to us with a product that worked on paper and frustrated everyone in practice. Patients booked in one tool, joined video calls in another, and their records lived in a third that none of the others could read. Every consult meant a clinician copying a name, a date of birth, and a complaint by hand from one screen to the next before the visit could even begin. The founders had real demand and real revenue, but the seams were starting to show, and they knew that the next stage, scaling the panel of doctors and opening a funding round, would not survive on a stack of off the shelf parts taped together.
Two numbers told the story. Roughly a third of booked appointments turned into no shows, because a single confirmation email was the only nudge a patient ever received, and slots that vanished at the last minute were slots a doctor could not refill. At the same time, clinicians were losing several minutes of every consult to manual data entry, which does not sound like much until you multiply it across a full day of patients and a growing roster of physicians. Underneath all of it sat a harder constraint. UAE health data carries strict expectations around where it lives and how it is handled, and a patchwork of foreign hosted tools gave the founders no clean answer when an investor or a regulator asked the obvious question about residency and privacy.
We replaced the patchwork with one product that a small senior team could own end to end. A single cross platform React Native app served both iOS and Android from one codebase, so a fix or a feature shipped to every patient at once rather than being rebuilt twice. Inside it, booking, secure video, records, and prescriptions finally lived in the same place and shared the same data. The pieces that mattered most:
We ran the build in tight two week loops with a clinician on the team standing in as our first user. One Thursday she walked us through a real consult on a pre release build, talking out loud while she went, and stopped on the visit notes screen because the field order did not match the way she actually questioned a patient. We reordered it that afternoon and shipped it the next morning. Small moments like that, caught while a doctor was holding the phone rather than reading a spec, are why the workflow ended up feeling built for the people using it instead of around them.
The headline
No shows came down 38 percent once reminders went live, which handed clinicians back slots they used to lose for good.
A single React Native codebase served iOS and Android, so every fix and feature reached all patients at the same moment.
Timed SMS and WhatsApp nudges with one tap confirm or rebook, built to recover slots that used to vanish silently.
In app WebRTC calls with encrypted media kept every visit between the patient and the clinician on the line.
Structured visit notes and prescriptions wrote straight into the records, so clinicians never re keyed a thing.
Data stayed on in region cloud hosting aligned to the UAE PDPL, encrypted in transit and at rest with audit logging on from day one.
The app opened in under two seconds, so a waiting patient or a clinician between visits never sat watching a spinner.
| Before | After | |
|---|---|---|
| Booking and records | Three disconnected tools | One app sharing the same data |
| No show rate | Roughly a third of appointments | Down 38 percent after reminders |
| Patient data entry | Clinicians retyped details by hand | Notes and prescriptions wrote in automatically |
| Data residency and compliance | Foreign hosted, no clean answer | In region hosting aligned to UAE PDPL |
Within three quarters of launch the app was carrying more than 12,000 video consultations a month, and it held a 4.8 rating across both stores while it grew, which for a healthcare app under real load is the part the team is quietly proudest of. The reminder flow cut no shows by 38 percent, turning a daily scramble to refill empty slots into a predictable schedule. Clinicians stopped retyping patient details and got those minutes back on every visit, and the app opened cold in under two seconds, so a patient in a waiting room or a clinician between consults never sat staring at a spinner.
consults a month
app store rating
patient no shows
app cold start
The reminders alone paid for the rebuild. Our no shows dropped by more than a third in the first month, so our doctors stopped staring at empty slots, and the in region hosting meant I finally had a straight answer when investors asked where our patient data lived.— Head of Product, a UAE telehealth provider
FAQ
The old setup sent one confirmation email and nothing else. We added automated reminders over SMS and WhatsApp, timed to reach patients shortly before each appointment with a one tap way to confirm or rebook. That single change recovered slots that used to disappear silently, and no shows fell by 38 percent in the first month live.
Yes. Patient data stays on in region cloud hosting, encrypted both in transit and at rest, with privacy by design handling aligned to the UAE PDPL and sector expectations. Audit logging was switched on from day one, so the founders had a clear story for both regulators and investors about where data lives and who touched it.
A single React Native codebase let a small senior team ship iOS and Android in parallel, share the business logic, and release fixes to both platforms at the same moment. That kept build and maintenance cost down without giving up the native feel, and it is a big part of why the app holds a 4.8 rating and opens in under two seconds.
Book a free consultation with our engineers.