Arabic first is not translating the screen: what changes when an experience is designed in Arabic from the root?

What is the difference between translating a children's screen and designing it in Arabic from the root?

Translating a screen swaps the words and leaves everything else exactly as it was: the rhythm, the humor, the sentence length, and the direction a child's eyes travel across it. Arabic first means all of those elements are designed in Arabic from the first line of the story, so nothing is left needing a later transfer. The difference between the two is not a matter of translation quality; it is a decision made earlier than translation altogether: which language the story is written in the first time.

This difference looks like a detail until it is seen in one concrete example. A character's name, a common saying, or a sentence that ends on a joke: each of these details carries a decision made in a specific language. Carrying it into another language once it is finished resembles trying to carry a joke you heard in one language into another: the words come through and the reason to laugh disappears.

What elements of language get lost in pure translation?

Elements far broader than a single word decide what actually reaches a child, and each one is a design decision, not a minor linguistic detail:

• Word length. An Arabic sentence often runs longer in characters than its English counterpart, and a screen originally designed for English text space crowds a longer Arabic text, which gets cut or shrunk with no real design review.
• Reading direction. An Arabic-speaking child's eyes move right to left, and a progress bar or a comic panel order carried over unchanged from a design that reads the opposite direction disrupts a story's sequence instead of serving it.
• Sound. A character's name may be written in Arabic letters yet still sound strange when spoken aloud by a child or a grandmother reading to them, unlike a name born with a familiar Arabic sound from the first moment.
• Linguistic age. A word that seems simple to an English-speaking child may sit far from an Arabic-speaking child's vocabulary at the same age, because the two languages are not acquired word for word on the same path.
• Register. Choosing between literary Arabic and a spoken dialect is a decision in itself: a warm literary register close to a child's heart, a dialect close to how a family talks, or a deliberate mix depending on the moment.
• Humor. Many jokes rest on wordplay or a cultural reference, and translation does not carry them into another language; they need a new joke built from the target language's own material.
• Names of things. A toy, a place or a food carries a mental image for a child who grew up around it, and may carry nothing for another child if it is copied literally from an environment foreign to them.
• Proverbs. The short wisdom passed between generations usually lives in a folk or spoken saying, and these proverbs rarely have a literal equivalent in another language carrying the same weight and meaning.
• Family context. The terms family members use to address each other, and each person's role, differ from one setting to another, and a story that assumes a foreign family structure feels distant from an Arab child's own home.
• Occasions. A child's calendar of occasions differs from the calendar a story was originally written for, and a story celebrating an occasion a child does not know loses part of its closeness to them.
• Story rhythm. The pace of events, and how often a phrase or scene repeats, are habits that differ between storytelling traditions, and a tradition copied literally from another can feel unfamiliar in rhythm to a child raised on a different one.

What does the result look like comparing translated to designed in Arabic?

The following pairs are illustrative examples to make the difference concrete, not specific real cases:

• Translated (illustrative example): a character's name stays as it is in Arabic letters, sounding strange every time it is said. Designed in Arabic (illustrative example): a name born with a familiar sound, understood by a grandmother the first time she hears it.
• Translated (illustrative example): a joke built on English wordplay gets explained in a footnote instead of making anyone laugh. Designed in Arabic (illustrative example): a new joke built from Arabic wordplay, making a child laugh directly with no explanatory footnote.
• Translated (illustrative example): a familiar foreign saying translated literally, reading as a strange sentence carrying none of the original wisdom's weight. Designed in Arabic (illustrative example): an Arabic saying carrying the same meaning, one a child already knows from home.
• Translated (illustrative example): a progress bar moves left to right exactly as originally designed. Designed in Arabic (illustrative example): the direction is fully reversed to match a child's right-to-left reading, with every surrounding element following the same direction.
• Translated (illustrative example): a foreign seasonal occasion appears on a game's calendar as is, with no clear meaning for the child. Designed in Arabic (illustrative example): an occasion the child's own home knows, such as the start of the school year, takes its place.

What design decision changes because of this difference?

The first decision is where writing itself happens: the story is written in Arabic starting from the first storyboard, not after an English version is already finished. This is what our process page describes when it says "Arabic first" means the experience is written in Arabic from the storyboard onward, rather than translated into it once finished. The second decision is who judges the result: a name, a joke or a saying is not locked in before an Arabic-speaking child hears it and their real reaction is observed, rather than the team's own opinion about how good the wording sounds. Where the language and culture decision sits among the six lenses and the methods we choose from per project is explained further on our expertise page.

Checklist: how do you examine your product's Arabic from the root?

• Was the story written in Arabic first, or translated into it after being finished in another language?
• Was every character's name heard in its Arabic sound in front of a child before being locked in?
• Did at least one joke rest on Arabic wordplay, rather than a footnote explaining a foreign joke?
• Does the design team know a child's own household occasions, or does it rely on an imported calendar of occasions?
• Does every visual element's direction, from the progress bar to comic panel order, match right-to-left reading?

What are the limits of this discussion?

This is a description of an internal design practice, not a published comparative linguistics study. This article does not claim every language element named here applies equally to every project or every age band, nor does it offer a rigid rule that replaces testing each story on its own in front of Arabic-speaking children. The examples marked above are entirely illustrative, and any real check of a product's Arabic needs direct observation, not theoretical assumption alone.

Where should you start?

If you are building an experience for an Arabic-speaking child, do not start from "how do we translate this?" Start from "how would this actually be said in Arabic?" The difference between the two questions shows up in every detail after it. This article covers one detail within five broader gaps discussed in the Arabic childhood content gap, specifically the language gap, and where it sits among the other gaps is explained fully there. You can also read how an idea is born here to see where the language decision begins within the full path, or tell us about your project through the Start a project form.

References

This article is an internal design practice piece (evidence level: D), and does not cite a specific external linguistic study. Literary Arabic as a register distinct from spoken dialects is a well-known phenomenon in Arabic linguistics, usually studied under the term "diglossia," named here as a general known concept rather than a specific research finding.

Quick questions

Is arabizing names alone enough to make an experience Arabic?

No. Swapping a name alone leaves the cultural structure, rhythm and humor exactly as they were born in another language. A name is one detail among many, and changing it alone gives a surface feeling of locality rather than real locality.

Why isn't a language review after the design is finished enough?

Because a language review fixes a sentence, not the decision it was built on. Story rhythm, eye direction and how much text a screen allows are design decisions made before any sentence, and they are hard to change once a screen is frozen.

Does this mean literary Arabic is always the only right choice?

No. A warm literary register suits most content aimed at early and middle childhood, but other moments need a register close to how a family actually talks. The decision rests on age band and moment, not one rule applied to everything.