Skip to content

Traveln.ai · Client project

A dashboard that works in two directions.

The Arabic version of the Traveln B2B dashboard. Mirrored data tables, a numeral hierarchy, and a workflow where operators work in Arabic and clients receive an English proposal.

Product
SaaS and dashboard · Travel
Role
Lead product designer
Scope
RTL adaptation, bidirectional data tables, numeral system, bilingual output
Platform
B2B web application, Arabic
Year
2026 · In testing
SaaS and dashboardArabic & RTLAIDesign system
A laptop and a monitor showing the Traveln B2B dashboard in Arabic, right to left

The Arabic sibling of the Traveln B2B dashboard, for Arabic-speaking operator teams. A consumer app mirrors layouts. An operations dashboard mirrors data: dense tables, charts, mixed-script fields and system identifiers all fighting over reading direction. This is where a direction-aware design system earns its keep.

The operations dashboard in Arabic, fully mirrored
The dashboard, fully mirrored, with the sidebar on the right.

The hard problems

Every table row mixes Arabic client names, Latin booking references, currency amounts and dates. Column order, sort affordances, status chips, checkboxes and pagination each have a natural side that flips, except when it should not. Getting a dashboard's direction wrong does not just look off. It slows down the exact people the product promised to make faster.

Key decisions

  1. A numeral hierarchy, not a numeral rule.

    Business figures such as revenue, bookings and trip values use Eastern Arabic numerals with the dirham mark (٣,٦٠٠ د.إ), because operators read and report them in Arabic. System identifiers such as BK-1043 stay Latin: they are codes, not language, and they must match emails, exports and support tickets.

  2. Data tables mirror completely.

    Column order, row anatomy, action buttons, bulk selection, status chips and pagination all flip. The table pattern from the English dashboard was rebuilt direction-aware once, and every log screen inherited it.

  3. Arabic in, English out.

    The sharpest challenge was a workflow, not a screen. Operators build trips in an Arabic interface and the product generates a polished English proposal for the client. The preview holds both on one screen: Arabic controls on the right, the English document on the left. The operator never leaves their language and the client never sees it.

  4. AI trip generation speaks operator Arabic.

    The prompt composer, its chips and its templates are written in Arabic, so the AI workflow feels native rather than translated.

Booking logs in Arabic with Latin booking references
Booking logs: Arabic data, Latin references, chips and bulk actions on their correct sides.
AI trip generation in Arabic
AI trip generation, with Arabic chips and templates.
The brief wizard in Arabic
The brief wizard.
Proposals managed from the Arabic interface
Proposals: Arabic controls, English documents.
Client management in Arabic
Client management.

Have a product like this?

We reply by email to set up a call. Most projects start with a short conversation and a scoped proposal.