01 / Localization workflow
Keep stable layers underneath every language
Build the shared composition first, then attach language variants to stable text and asset layers. Product names, legal marks, and translatable claims should remain separate when they follow different rules.
A locale can replace both the marketing message and the underlying app capture without forking the whole page. Shared layout corrections then remain shared.
- Name pages and text layers before translation begins.
- Add only languages planned for the release.
- Review the longest copy at the smallest selected output.
02 / Localization workflow
Use CSV as a controlled hand-off
Export translation CSV after page and layer identities are stable. Translators can edit the copy while the project retains the identifiers needed to return each value to the correct layer.
On import, review missing, duplicate, or unknown identifiers. Row order should not be treated as identity, and text layers should not be renamed during an active hand-off.
03 / Localization workflow
Validate the complete language-and-size matrix
A correct source-language preview does not prove that every translated output is complete. Preflight checks missing translations and assets, unsafe bounds, counts, output resolution, and store-specific format rules across the selected matrix.
Resolve errors before batch export, then inspect the release folder as a complete deliverable rather than a collection of individually plausible images.