Product Design  ·  01

Allianz Digital Health
Ecosystem

A free telemedicine feature that nobody used — redesigned into the app's primary health touchpoint, integrating 3 independent backends for 4M+ insurance users.

Company
Allianz Turkey
Role
Product Designer · End-to-End
Platform
iOS & Android
Timeline
2023–2025 · 2 Years
Team
Solo Designer · 3 Squads
The Problem
A paradox hiding in plain sight

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.

Dr. Allianz existed. It was free. Almost nobody used it. The problem wasn't the product — it was where it lived.
Discoverability The feature was buried 3+ taps deep inside the Sağlığım tab sub-menus. Users had no reason to look there, and no signal it even existed.
Fragmentation Dr. Allianz, Remote Examination, and Appointments were scattered across different parts of the app — no unified entry point, no coherent health journey.
Integration The Bulut Klinik flow required a hard context switch to webview — breaking native feel and increasing drop-off at the most critical moment in the flow.

Design Constraints

  • Work within the existing Allianz'ım component system — no new custom components
  • 3 independent backends (AZS · Bulut Klinik · Allianz) each with separate APIs and logic
  • App redesign running in parallel — design had to work for both states
  • AZS provizyon approval had strict backend requirements before any action

Edge Cases in Scope

  • Appointment limit exceeded → route to Dijital Doktorum upsell or info screen
  • BES customers previously routed to Vivy → migrate to Dr. Allianz flow
  • KVKK / data privacy requirements for appointment booking
  • 18+ age rules and family policy delegation logic
The Solution
One hub. Three modules. Zero webview breaks.

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.

Module 01
Dr. Allianz — Video Consultation
7/24 free video call with a doctor. AZS provizyon approval → Bulut Klinik webview → consultation. No diagnosis or prescription.
Module 02
Remote Examination — AI Booking
Branch selection, doctor listing, and slot availability served natively from Bulut Klinik API. Full appointment flow in-app.
Module 03
My Appointments — Management
Past and upcoming appointments via AZS. Join link activates 5 min before session. Color-coded active vs. past states.
Design Process
From analytics signal to shipped product
01
Analytics review & brief alignment
Reviewed usage data that confirmed the discoverability gap. Aligned with PM and stakeholders on the two core objectives: visibility and native integration. Mapped existing feature locations across the app to understand the full scope of fragmentation.
02
Service architecture mapping
Mapped all 3 backend systems and their touchpoints before touching a single screen. Identified where AZS provizyon sat in the flow, when Bulut Klinik API took over, and how the Allianz backend handled appointment records and policy data.
03
Entry point strategy
Decided on two static entry points using existing components: a homepage CTA block and a Sağlığım tab placement. This alone reduced navigation depth from 3+ taps to 1 — the highest-leverage change in the entire project.
04
Flow design & edge case coverage
Designed all three module flows end-to-end using existing components. Each screen was mapped to its backend trigger. Edge cases — limit exceeded, BES routing, policy-based branching — were designed explicitly, not left to dev interpretation.
05
Parallel redesign alignment
With a full app redesign running simultaneously, screens had to work in both the legacy and new design states. Designed for the new system, provided specs for the legacy state as well to unblock development.

↑ Annotated screen designs coming soon — mockups in progress.

Key screens: Hub entry point · Dr. Allianz flow · Appointment booking · Edge case states

Before & After
From buried to front and center

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.

Before Feature fragmented — low prominence, no unified health entry point
Eski ana sayfa
No digital health entry point anywhere on homepage
Must tap Sağlığım tab first — 2+ taps minimum
Eski sağlığım
6 other services listed before telemedicine
"Dr. Allianz'la Görüş" at very bottom — same weight as IBAN update
Eski hub ekranı
Hub existed but no prominent path led users here
Bulut Klinik triggered jarring webview context switch
3+
taps to reach
2
scattered locations
↓
low engagement
Webview
context break
Design intervention
After Redesigned with existing Allianz'ım components — two entry points, unified hub, native integration
Yeni ana sayfa
"Uzaktan Sağlık" promoted to homepage quick-actions
1 tap to reach the full digital health hub
Yeni sağlığım
Telemedicine visually elevated — distinct from admin tasks
Static placement in Sağlığım tab — always reachable
Yeni hub
All 3 modules on one screen — no scrolling needed
Native Bulut Klinik API — seamless, no webview break
1
tap to reach
+65%
CTR increase
15s→4s
time to action
Native
API integration
Impact
What changed after shipping
Discoverability & Access
+65%
CTR on Digital Health entry
vs. buried "Dr. Allianz" button
15s → 4s
Time to Action
Reaching appointment booking
4M+
Users reached
Allianz'ım app base
Usage & Conversion
+40%
Active feature usage
Online consultation engagement
−25%
Drop-off rate
Branch selection → booking
3
Backends unified
AZS · Bulut Klinik · Allianz
Business Value
+15%
In-app CSAT
All health services in one hub
+12%
Upsell potential
Dijital Doktorum policy redirects
0→1
Built from scratch
Existing component system only
Reflection
What I'd do differently

What worked well

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.

What I'd approach differently

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.