CASE STUDY 03 / 08
Telemedicine

Robov.

From booking an appointment to joining the conversation.

An appointment and telemedicine platform for physicians and private clinics, bringing patient communication and browser-based video consultations into the same experience.

My role

Frontend development & architecture lead

Context

Husan

Timeline

Oct 2022 onward

01 / The challenge

The problem worth solving.

A consultation should feel like a natural continuation of an appointment. The product needed clear media-permission flows and reliable browser behavior, with a frontend that could evolve independently of a particular video service.

02 / My contribution

Where I took ownership.

  • Led frontend architecture and implementation.
  • Built the main appointment and telemedicine journeys.
  • Designed media integration boundaries and device-permission behavior.
03 / The approach

Decisions behind the experience.

01

A connected patient journey

Implemented appointment and consultation flows that preserve context as patients and physicians move into a live session.

02

Clear media states

Handled camera and microphone permissions, failure states, and browser compatibility so users receive understandable feedback.

03

An adaptable consultation layer

Separated video-service integration from product code, keeping the interface and application flows independent of provider-specific details.

04 / What this work enables

Engineering that serves the workflow.

The frontend connects scheduling and live care in a cohesive flow, while an independent consultation layer allows the underlying integration to change without spreading those changes through the product.

Discuss a similar challenge