RTL, Script Speed and Gesture Risk in Playable Localisation

Text expansion, RTL layout and script reading speed break playables in ways a translation pass will not catch, a working checklist for 2026.
Our 2025 guide, Localisation Inside the Playable Ad: Text, Gesture, Pacing, argued that a native reviewer catches problems a translator cannot, and made the case for testing gesture and pacing as market-specific variables during QA. A year on, that argument still holds, and the stakes have grown: Sensor Tower's State of Mobile 2026 report, published in January, put playables at 13.3% of creative share, nearly double the year before, which means a localisation shortcut now compounds across more builds and more markets than it did when playables were a smaller slice of the mix.
Most localisation requests that land on a playable production queue are still treated as a string swap: pull the English copy, send it to translation, drop it back in. The build usually still works. It usually still tests badly, because the parts of a playable that actually carry meaning in a new market are rarely the words, and the failures worth naming this year are more specific than gesture and pacing in the abstract: text expansion, script direction, and reading speed by script.
Where text expansion and RTL layout break first
German and Finnish routinely run 30 to 40% longer than English for the same instruction. Arabic and Hebrew need right-to-left layout, not just right-to-left text within a left-to-right frame. A CTA button sized for "Tap to play" will clip or wrap "Tippen zum Spielen", and a wrapped CTA reads as broken, not translated. Build button and instruction containers with expansion headroom from the first English draft, not as a fix applied after a locale fails QA.
Gesture is not universal
A pointing-hand cursor, a swipe arrow, a thumbs-up end card, a circling motion to indicate "tap here": all of these carry different or offensive meanings in different markets. The thumbs-up is a real risk in parts of West Africa and the Middle East. An open palm gesture reads as an insult in some Latin American and West African markets. Tutorial iconography that relies on a specific hand gesture should be reviewed market by market before it ships, not assumed neutral because it tested fine in the US and UK.
Pacing is a translation problem too
A playable's timing is tuned for a reading and reaction speed calibrated to the source language. Japanese and Korean players commonly need more time to parse an on-screen instruction written in those scripts at the same information density as English, because character-based scripts carry more meaning per glyph but require more visual processing per character for a first-time reader. If a tutorial arrow disappears after two seconds in every locale, a market with a naturally slower first-read time loses the instruction before the player has parsed it, and the drop-off shows up in playable-to-install as "the mechanic didn't land" when the actual fault is timing.
Colour and iconography carry cultural weight
Red reads as danger or a warning in most Western markets and as luck or celebration in Chinese markets. A red "fail" state in a puzzle playable can send an unintended signal in a build targeted at China. Currency symbols, calendar icons and clock faces also carry local conventions worth checking rather than assuming.
A working checklist
Before a localised build ships, run it through:
- Text containers tested with the longest expected string in the batch, not the English placeholder
- Gesture and iconography reviewed against a market-specific list, not a single global asset library
- Tutorial timing tested with native speakers of the target script, not extrapolated from English pacing
- Colour and symbol choices checked against local convention for the specific market, not the region
None of this needs a bigger budget. It needs the localisation pass to happen before the build is locked, with someone who reads the target language actually playing the build, rather than a translator handing back a spreadsheet of strings for an engineer to paste in.


