What I owned
Led design end-to-end across patient and clinic apps, iOS-first, with the period tracker as a core feature.
Back to work2 min read02 / 05
Taa Marbuta · 2024HealthTech · 0→1 · RTL-first · 2024
Two apps. One health experience designed Arabic-first.
Led an RTL-first female health product from zero across patient and clinic apps, iOS-first, designed for Arab women.
Client-provided research made the first session a trust-sensitive moment, not just onboarding.
2
apps designed
- Role
- Solo UX/UI Designer
- Duration
- 2–2.5 months
- Platforms
- Mobile · iOS-first
- Industry
- HealthTech · 0→1
The setup
Taa Marbuta was designed for Arab women navigating local health contexts. I worked as the solo UX/UI designer with two mobile developers, a backend developer, and a project manager. Language, cultural sensitivities, booking, and follow-up shaped the product constraints from the start.
Role & constraint
The constraint
RTL-native from day zero, with trust signals and booking decisions designed for Arab women.
The problems
What was actually broken.
Problem 01
Client research: two-week abandonment
Client-provided market research made trust and onboarding quality central to the first session.
Problem 02
Client research: phone booking remains common
The digital booking flow had to make the next step clearer than a phone call.
Problem 03
Trust shapes booking decisions
Interviews identified doctor credentials, verification badges, and review context as part of the booking decision.
Problem 04
Clinics need appointment control
The clinic app needed tools for the working day, not just a display of bookings.
The decisions
From evidence to a design decision.
Research
Mapped why women abandon, trust, onboarding quality, and the gap between a phone call and a digital booking.
Design RTL-first
Built an Arabic typography hierarchy and laid every flow out RTL-native, never retrofitted from an English layout.
Two mental models
Split patient and clinic into distinct apps, each tuned to how that user actually thinks and works.
The solutions
What I actually did about it.
01Solution 01 / 04
RTL-first from day zero
The Arabic experience was the primary experience, not a retrofit, not a translation.
Built an Arabic typography hierarchy optimized for health-content readability, with every layout designed RTL-native.
Native to Arab womennot localized
preview soon
02Solution 02 / 04
Trust-building UI patterns
Doctor credentials, clinic verification badges, and review authenticity signals woven throughout the booking journey.
Confidence designed into every decision moment
preview soon
03Solution 03 / 04
Period tracker as the core
Client internal analysis reported 3× higher engagement with period-tracker features.
Calendar → daily log (expanded + collapsed) → history → predictions, all inside a dedicated Health Hub.
A daily-use anchor in the product
preview soon
04Solution 04 / 04
Two apps, two mental models
Patient app (5-tab) and clinic app (4-tab), each with flows tuned to how that user researches and books.
Patient + clinic appsiOS-first
preview soon
By the numbers
2
apps: patient + clinic
×3×
client-reported period-tracker engagement
%69%
client-provided two-week abandonment research
Project period: 2–2.5 months
Arabic-first, not a translated afterthought.
Gallery
A closer look.
Key visuals from the project, then the individual decision screens. Full-fidelity shots of those are coming soon.
Reflection
What I'd carry forward
For sensitive health journeys, I would treat credentials, verification, and review context as part of the booking decision, not decorative UI.
Related work