Arabic App Store Screenshots: An RTL Review Workflow

Capture the Arabic interface before composing the artwork

Open the shipping app in Arabic and prepare the same example state used by the rest of the release. A translated marketing headline above an English settings screen may leave a visitor unsure about what is localized. Caption translation in Shipshot edits the text you place around the capture; it does not replace words baked into the screenshot. If a feature remains English-only, describe that accurately rather than painting a translated interface over it.

1. Capture each relevant screen in the app’s actual Arabic locale.
2. Use fictional but plausible names, dates and amounts throughout the set.
3. Check whether the feature and content are available in the markets you plan to serve.

Inspect connected letters, punctuation and mixed text

Start with the longest caption and one containing a Latin product name or a number. Check whether the chosen font connects letters properly, whether punctuation lands in the intended place, and whether a line break splits the phrase awkwardly. A visually centered text box can still contain a confusing reading sequence. Treat short embedded Latin words as part of the sentence that needs review, not as a reason to reverse the whole image.

1. Review a caption containing an Arabic phrase, a numeral and your app name together.
2. Inspect the exported PNG as well as the editable canvas; font substitution can change the result.
3. Have an Arabic speaker read the final composition aloud in its intended order.

Decide what should change direction

Do not mirror a finished screenshot automatically. Text, logos, photographs and real UI can become wrong when the entire image is flipped. Work from the app’s real localized interface and adjust the surrounding composition separately. If the English story relies on a device pointing toward a caption, consider moving the caption or device rather than reversing all pixels. Keep graphs, maps and other directional information faithful to the product.

1. Separate the real app capture from decorative arrows and background elements.
2. Review each visual cue by meaning: does it imply navigation, sequence or motion?
3. Check the actual store preview before assuming how visitors will move through the images.

Give the reviewer complete files and a clear approval task

Send the composed set in order, alongside the intended meaning of each caption. Ask for language corrections, layout problems and product mismatches separately so a copy edit is not mistaken for final approval. After changes, regenerate every affected target and compare the exported files with the approved preview. Keep the final file names associated with the language, platform and build you reviewed.

1. Record which Arabic wording was approved, who reviewed it and which release it belongs to.
2. Confirm all screenshots are present for the selected device classes.
3. Upload the files manually to the appropriate store localization and inspect the listing preview.

Review checklist

Questions to ask before handoff