Bilingual Asset-Financing Journey
A seven-step financing journey had to remain clear and consistent across Arabic RTL and English LTR experiences.
Journey design, responsive UX, bilingual interaction patterns, stakeholder collaboration, and frontend-aware delivery.
Delivered a unified 7-step financing journey operating consistently across Arabic RTL and English LTR layouts.
Context
A Saudi financial-services product required a seven-step financing journey that worked in both Arabic RTL and English LTR.
Challenge
The experience needed to preserve a consistent mental model while direction, alignment, reading order, and responsive behaviour changed between languages.
My Role & Responsibility
I worked on journey design, responsive UX, bilingual interaction patterns, stakeholder collaboration, and frontend-aware delivery.
The Flow I Had to Understand
The financing experience was structured as a seven-step journey. My focus was to keep progression, information hierarchy, actions, and orientation clear across both language directions.
Seven-step bilingual financing journey
Key Decisions
Decision 01 — Design directionality as behaviour, not translation
Treat RTL as an interaction and layout requirement rather than changing text while leaving the interface logic untouched.
Decision 02 — Preserve the same journey logic across languages
Keep the underlying seven-step progression consistent so language direction changed without creating two different products.
Decision 03 — Validate responsive behaviour in both directions
Consider spacing, alignment, navigation, form structure, and content flow across both LTR and RTL layouts.
Why Those Decisions Mattered
Bilingual UX becomes fragile when RTL is applied at the end. Designing directionality into the system earlier reduces inconsistency and makes the experience easier to maintain.
The Improved Experience
The final direction provided one coherent financing journey that could adapt between Arabic RTL and English LTR while maintaining consistent progression and responsive behaviour.
Constraints & Trade-offs
The experience had to balance bilingual layout behaviour, financial information density, responsive layouts, stakeholder requirements, and practical frontend implementation.
Collaboration & Implementation
I worked across design and development teams to ensure bidirectional layouts, directional CSS properties, and responsive behavior met both user expectations and technical constraints.
Outcome
Delivered a unified 7-step financing journey operating consistently across Arabic RTL and English LTR layouts.
Reflection
“This project strengthened my view that RTL is a product-system concern. It affects layout, hierarchy, motion, controls, and implementation—not just typography.”
Confidentiality Note
* This case study has been anonymized to respect client confidentiality. The company identity and original product screenshots are not shown. Flow diagrams are used to explain the actual problem, design decisions, and outcomes. Additional context can be discussed privately during an interview.