Your Arabic AI feature is an English one with translated strings.
Bilingual Arabic AI engineering: native RTL interfaces and language-aware voice pipelines, built for Arabic rather than translated into it.
Three signs Arabic was bolted on, not built in
- The Arabic UI is the English layout mirrored, not a layout actually designed right-to-left.
- The voice agent's endpointing timing was tuned in English and just reused for Arabic, so it cuts users off mid-sentence.
- Arabic copy reads like it was machine-translated, because it was.
How a bilingual product actually gets built
Use CSS logical properties, not a mirrored second stylesheet
margin-inline-start, padding-inline and inset-inline throughout, so a layout works in RTL without a second maintained codebase.
Tune endpointing per language, not per default
Arabic speech carries different pause patterns than English — silence thresholds are set and tested separately, with a measured endpointing penalty where one exists.
Write Arabic copy natively, never machine-translate
Shorter sentences, no calques from English phrasing — written for an Arabic reader, not translated for one.
Keep numbers, code and diagrams LTR inside an RTL page
Direction is set explicitly per element, so a phone number or a code block doesn't reverse itself inside an Arabic layout.
Test the full flow in Arabic, not just the strings
Voice, layout and copy are verified together in Arabic before launch, not assumed to work because the English version did.
Muhawir: bilingual by architecture, not by string table
A bilingual voice interview practice agent where Arabic and English are separately tuned pipelines — distinct endpointing, distinct synthesis voices, distinct native copy — not one English pipeline with a translated layer on top. This site itself ships the same way: full RTL layout, native Arabic copy, and language-aware voice demos.
Concrete deliverables
A fully working RTL layout
Every page, not a partial mirror — built on logical CSS properties from the start.
Language-aware endpointing
Silence thresholds tuned and measured separately for Arabic, with the penalty stated, not hidden.
Natively written Arabic copy
No machine translation — copy written for an Arabic reader from the start.
A verified bilingual toggle
Language and direction switch cleanly with no layout break, tested both directions.
The two questions every team asks
"Will Arabic quality actually match English?"
Only if it's treated as its own build, not a translation pass at the end. That's the entire premise here — separate endpointing, separately written copy, and a layout designed for RTL from the start, rather than English shipped first and Arabic patched in afterward.
"Isn't RTL just flipping the CSS?"
Visually, mostly — but numbers, code, phone numbers and diagrams need to stay left-to-right inside an RTL page, and getting that inconsistent is a common tell of a rushed job. Logical CSS properties handle the layout flip cleanly; direction overrides handle the exceptions explicitly.
Bilingual work starts at $6,000
The Build tier covers a full bilingual voice or agent system end to end, deployed, across 4–8 weeks. Full tiers and payment terms are on the pricing page.