iOS and Android
Mobile app localization
Scope mobile app localization before release.
Prepare app text, store listings, onboarding, and notifications with screen context, character limits, and review owners confirmed.
UI, store, onboarding, alerts, support
Coverage reviewed during scope
For localization work, scope starts with files, screenshots, glossary, character limits, reviewer owner, and release path. The delivery file must match the product import workflow.
What this page helps you scope
- Mobile UI strings, onboarding flows, app store listings, push notifications, and support content.
- Character limits, screenshots, and device context for short strings.
- Release updates where new strings must match existing terminology.
- Multilingual app content packages prepared for import.
What you receive
- Localized mobile app strings.
- Store listing translation.
- Review notes for character limits and context.
Questions teams ask first
What app files can be localized?
Common exports include string tables, JSON, CSV, XML, XLIFF, and spreadsheet files, depending on the product workflow.
Should app store content be handled with UI strings?
It can be, but store copy should be scoped separately because search terms, screenshots, and buyer intent differ from in-app text.