A free telemedicine feature that nobody used — redesigned into the app's primary health touchpoint, integrating 3 independent backends for 4M+ insurance users.
Allianz Turkey's product team identified a striking paradox in their analytics: the app offered a free, 7/24 telemedicine consultation feature — yet engagement was critically low. The data was clear. Users simply weren't finding it.
The brief I received had two objectives: make digital health a first-class citizen of the app, and integrate Bulut Klinik's API natively into the experience — eliminating the jarring webview handoff that broke the flow.
Rather than patching the existing feature, I designed a Digital Health Hub — a dedicated landing layer that unified all health touchpoints under a single, prominent entry point. Two static placements were added: one on the Allianz'ım homepage, one in the Sağlığım tab. Navigation depth dropped from 3+ taps to 1.
The hub presented three distinct modules, each with its own flow, backend logic, and edge case handling — all feeling native within the existing app design system.
↑ Annotated screen designs coming soon — mockups in progress.
Key screens: Hub entry point · Dr. Allianz flow · Appointment booking · Edge case states
The same feature. The same users. A completely different result — driven entirely by where it lived in the app. Both versions built on the same Allianz'ım component system.
Mapping the service architecture before any screen design was the right call. It prevented redesigns mid-flow when backend constraints surfaced. Using existing components kept dev handoff clean and fast.
With access to usability testing, I'd have validated the hub entry point placement with real users before committing. The analytics showed low usage but not why — user interviews would have added depth to the problem definition.