# App Store localization glossary to keep screenshots consistent
Inconsistent screenshot wording across locales triggers rejections and confused users.
Contents
# Steps
- Lock a glossary for feature names.
- Keep CTA length limits per language.
- Avoid idioms that break in translation.
- QA screenshots against live build strings.
- Version the glossary with release tags.
# Field note
Write exceptions into a shared doc; weekly review only the outliers.
Reference hubs: cross-border headlines, US123, TT123.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Addendum: pilot on a small SKU set before scaling; keep dates, owners, and screenshots for audit. Revisit the checklist after every peak week.
Published by Facebook520 Cross-Border Navigation.