almatar · Design Systems

A multi-platform design system for MENA travel

Lead Design System Architect · 2026–Present · Travel / MENA

Architecting tokens, components, and RTL-native patterns across web, iOS, and Android — so product teams ship one coherent experience in Arabic and English.

almatar design system hero: English desktop flight listing beside Arabic light and dark mobile apps, with theme modes and button tokens

Travel in the MENA region is not a skin on a Western product. Arabic and English share the same surfaces. Dates refuse to abbreviate. Fare rules, baggage, and multi-city itineraries pack density into every card. Almatar needed a design system that could be the spine of web, iOS, and Android — not a file of components that drift apart the first time a squad ships under pressure.

Context

I joined as Principal Product Designer and later moved into Lead Design System Architect. The system work sits beside product ownership of core booking surfaces. The team around the system is intentionally small: myself, a graphics designer, an interaction designer, and front-end engineers. That scale forces clarity — every token and pattern has to earn its place.

Operating model: Design System Architect with graphics, interaction, and front-end roles feeding shared tokens and patterns into Flights Hotels, Growth, and other product squads — A small system squad beside product — one library for web, iOS, and Android.

What I owned

End-to-end architecture for a new design system: tokens and Figma variables, styles, components, patterns, and templates. Components are built to be LTR and RTL, auto-layout, foldable, extendable, and responsive. Nothing ships as “we’ll fix Arabic later.”

Token architecture, variables, RTL craft, and cross-platform proof unlock with the case password.

What the public story can say

Multi-platform token architecture, RTL-native components, and Principal → Lead DS Architect. Unlock for the full systems narrative and visuals.