Test the extremes
Preview the widest, narrowest, largest, and smallest selected outputs early. Look for changes in line wrapping, device-frame balance, safe-area pressure, and the amount of application UI still visible.
Fix shared problems in the base composition. Use an override only when solving the shared design would make other targets worse.
Add targeted size overrides
Per-size overrides can change position, dimensions, or visibility for an output that genuinely needs different treatment. Document the purpose through clear layer and page naming.
Avoid recreating the full scene in overrides. If most layers diverge, consider whether that device family needs a deliberately separate page design.
- Move text away from an unavoidable safe area.
- Hide decoration that crowds a compact output.
- Adjust a device frame when the screenshot becomes unreadable.
Set up languages
With Pro, add only the languages planned for the release and identify the source language. Text layers store language variants against stable page and layer identities.
Keep product names, legal marks, and translatable claims in separate layers when they follow different localization rules.
Exchange translations through CSV
Export translation CSV after page and text-layer names are stable. Translators can work with the copy while the project preserves the identifiers needed to return each value to the correct layer.
On import, review unknown, missing, or duplicate identifiers rather than assuming row order is meaningful.
- Do not rename text layers during an active handoff.
- Preserve Unicode content without spreadsheet-side substitutions.
- Review the longest variants at the smallest output.
Check every size and language
Preflight checks missing translations, layer bounds, assets, page counts, output resolution, and store-specific format rules across the selected sizes and languages.
Resolve the report before rendering final assets. A clean representative preview does not prove that every language-size combination is complete.
