Case study · Healthcare
A telemedicine app that works on a 3G connection in a rural clinic
Consultations kept dropping outside major cities. We rebuilt the client offline-first and made the video layer degrade gracefully instead of failing.
- Client
- Private healthcare group
- Industry
- Healthcare
- Region
- Singapore & Malaysia
- Duration
- 6 months
- Team
- 5 engineers, 1 designer
- Delivered
- 2024
The problem
The existing app assumed a stable connection. In the regional clinics that needed it most, consultations dropped mid-call and notes were lost.
Clinicians were re-entering patient history because the app could not queue writes while offline.
Patient data handling had to satisfy healthcare privacy requirements across two jurisdictions with different consent rules.
What we did
- 1
We moved to an offline-first architecture with a local encrypted store, queued mutations and last-write-wins resolution on a per-field basis.
- 2
The video layer now steps down from HD video to audio-only to an asynchronous voice note rather than dropping the session outright.
- 3
Consent was modelled per jurisdiction as data, so adding a third market became a configuration change rather than a release.
- 4
We ran two rounds of usability testing with clinicians and cut the consultation flow from eleven screens to four.
Tell us what you need built
Send over the brief, or just a rough description. We read every enquiry ourselves and reply within one working day, usually with questions before a price.