Preserve the role, not every line break.
Start with the reason each frame exists: establish the outcome, demonstrate the workflow or answer a concern. Tell the language reviewer which role must survive. Exact source wording and line breaks are less important than a clear, accurate argument.
Use screenshot storytelling to define that sequence before translation. When a frame has several competing jobs, resolve the source message rather than asking a translator to compress the confusion.
Plan for layout pressure.
Different wording can need different space. Leave room for captions to change without shrinking them into illegibility. Review hierarchy, wrapping and spacing in the final composition rather than treating the original design as an untouchable template.
The stress chart uses hypothetical caption lengths, not language-specific expansion averages. Actual line breaks depend on the words, typeface and layout. Test your final text; do not turn a generic percentage into a rule for every language.
Keep the depicted interface honest.
Confirm that UI language, labels and features match the experience users can access. If the localized interface is not ready, decide how to describe the available product accurately. Do not invent screenshots of functionality that has not shipped.
Record the app version used for capture and the owner who checked it. Read trust signals for the broader principle: the image should support the promise, not simulate proof.
Review examples without assumptions about a country.
Dates, units, sample names and practical scenarios may need adaptation, but the change should have a reason grounded in the product and audience. Ask a qualified local reviewer which details confuse or distract. Avoid decorative cultural references with no connection to the user’s task.
Keep sensitive or real user data out of example screens. The creative brief should say which demonstration data is approved and which product states the designer may depict.
Approve the exported assets.
Inspect final screenshots at realistic viewing size and compare them with the approved language brief. Check truncation, duplicated frames, inconsistent terminology and wrong-language assets. Ask a reviewer to explain the intended message without your commentary.
Follow readability checks and the localization QA process. Save the approved export set with clear locale and version labels, then verify what actually appears after publishing.
