Mobile product localization does not start with translating buttons. It starts with preparing the product for another language, culture, and set of user expectations. If technical context, plural rules, string length, date formats, or App Store and Google Play content are ignored, even an accurate translation can break the interface or reduce user trust. The workflow below shows how to plan app and game localization before entering a new market.
What is app localization and how is it different from translation?
|
For a mobile app, replacing English text with Ukrainian, Polish, German, or another language is not enough. Teams also need to account for string length, grammar and plural forms, number and currency formats, dates and time, forms of address, system messages, push notifications, onboarding, paywalls, error messages, marketing pages, and other user touchpoints.
Games add another layer: narrative, dialogue, humor, character and item names, subtitles, voice-over, variables affected by gender or quantity, UI constraints, and cultural references. That is why game localization usually requires more context and more creative adaptation than straightforward interface translation.
Key stages of mobile app or game localization
1. Choose target markets, languages, and locales
Start with locales, not just languages. Portuguese for Brazil (pt-BR) and Portuguese for Portugal (pt-PT), for example, are different language-region variants. Locale affects terminology, date and currency formats, units, forms of address, and some legal or marketing wording. For products aimed at Ukraine, Ukrainian should be planned as a complete localization rather than treated as a minor variation of another Slavic-language version.
2. Check whether the product is localization-ready
Before translation, run a short i18n audit: are all user-facing strings externalized into resources, is text embedded in code or images, are plural forms, variables and placeholders supported, and are sentences being built from fragments? Android recommends separating localizable resources from app logic, while Apple uses string catalogs and localized resources for language and regional variants. Good internationalization reduces expensive fixes after translation is integrated.
3. Prepare files, context, and terminology
A translator needs more than a spreadsheet of strings. A strong localization package includes resource files or a TMS export, a current build or test access, screenshots, screen descriptions, a brand glossary, Tone of Voice guidelines, a do-not-translate list, and rules for variables. For games, add a character bible explaining who is speaking, to whom, in what situation, and with what personality and emotion.
4. Translate, localize, and transcreate
This stage covers UI, system text, help content, tutorials, notifications, feature descriptions, and other content. Marketing CTAs, slogans, jokes, and narrative lines often need transcreation: preserving the intended function and emotion rather than the literal structure of the source. A glossary and translation memory help keep terminology consistent, especially for products that ship updates every week or month.
5. Integrate and run linguistic quality assurance (LQA)
LQA happens after localized text is returned to the app or game. Reviewers check truncation, line breaks, overlapping UI, fonts, variables, plural forms, incorrect context, untranslated strings, sorting, number formats, and right-to-left behavior. Apple specifically recommends testing localizations for clipping, truncation, layout overlap, and RTL formatting issues.
6. Localize App Store and Google Play listings
An app can be fully localized inside the product and still look foreign in the store. The name, subtitle or short description, full description, screenshots, promotional copy, and other available fields should match the language of the market and the product’s actual positioning. ASO queries should not simply be translated; they need to reflect how people in that market search for comparable products.
7. Release, collect feedback, and localize updates
Localization does not end with the first release. New screens, events, DLC, seasonal content, support text, and store metadata need to stay synchronized with the source version. The most reliable workflow uses stable string keys, tracks source changes, and gives linguists access to context and previously approved terminology.
Common mistakes that make app localization more expensive
The costliest mistakes are usually process errors rather than language errors. When translation starts before the product is localization-ready, fixes appear after integration and may require changes in code, design, and copy at the same time.
- Translating strings without context, screenshots, or explanations of variables.
- Building sentences from fragments or handling plural and gender logic manually.
- Designing fixed-width buttons for the source language and never testing longer translations.
- Leaving push notifications, email, help-center content, paywalls, text-in-image assets, or store listings outside the localization scope.
- Using one literal translation for every regional variant of the same language.
- Releasing a locale without final LQA on real screens and user flows.
Practical checklist: what to send a localization provider before kickoff
The more complete the starting package, the fewer clarification loops and the lower the risk of missing the release date. For an initial estimate, prepare:
- target languages and countries;
- resource files or a string export with word/segment counts;
- screenshots or a test build;
- glossary, brand guide, and preferred Tone of Voice;
- platform list: iOS, Android, Unity, Unreal, or another stack;
- code-freeze / release date and the process for sending updates.
What determines localization cost and turnaround time?
App localization pricing is not based on word count alone. The estimate can depend on the language pair, volume of new and repeated segments, terminology complexity, number of locales, file formats, transcreation, editing, LQA, screenshot or graphic work, and, for games, dialogue, subtitles, and voice-over. Timing also depends on how clean the source resources are and whether testing in a build is required.
Instead of asking for a quote to “translate an app,” send the resource package and a short scope. A provider can then separate linguistic work, editing, testing, and additional tasks, giving the client a clearer budget and delivery plan.
How to choose a localization partner in Ukraine
For an IT company, the provider must be able to manage the process as well as the language: accept structured files, preserve placeholders and tags, maintain terminology, organize editing, work with context, and return files in the agreed format. Ask who performs LQA, how source updates are handled, and what is included in final QA.
Admiral Translation Bureau lists IT translation, technical documentation, marketing translation, and website localization among its services. According to the company website, Admiral operates through a network of 120+ offices in Ukraine and offers a fully online ordering process; its translation quality processes are presented as compliant with ISO 17100:2015 and ISO 9001:2015. For a digital product, this means the linguistic part can be coordinated remotely, with related corporate, technical, or marketing translation added when needed.
Notarization, apostille, or legalization are not required for interface strings. They may only be relevant to separate corporate documents, powers of attorney, certificates, or other paperwork prepared in parallel for international expansion.
FAQ: mobile app and game localization
How is app localization different from ordinary translation?
Translation transfers meaning into another language. Localization also adapts terminology, formats, interface behavior, graphics, cultural elements, and user flows, and verifies how the translated content works inside the product.
Can we localize only the iOS or only the Android version?
Yes. A scope can cover one platform, one locale, or a specific module. If iOS and Android share much of the same copy, however, a common terminology base and synchronized update workflow usually reduce inconsistency and rework.
Is LQA necessary after translation?
For release-quality localization, it is strongly recommended. Only the build reveals truncated buttons, wrong context, missing strings, font issues, plural or variable problems, and locale-specific formatting errors that may not be visible in a spreadsheet or CAT/TMS environment.
How long does mobile app localization take?
There is no universal turnaround time. It depends on content volume, number of languages, source readiness, subject matter, editing, transcreation, and LQA requirements. A reliable timeline can be set after reviewing the files and release calendar.
Can localization be ordered remotely from anywhere in Ukraine?
Yes. Admiral offers a fully online process: clients can send materials remotely, receive an estimate, and coordinate the project without visiting an office. The company also has a network of physical offices in cities across Ukraine for clients who prefer in-person service.
Conclusion
High-quality mobile app and game localization is a managed workflow at the intersection of language, UX, and engineering. Projects run more smoothly when the product is internationalization-ready, translators have context, terminology is approved before translation starts, and the localized build passes LQA before release. To assess the scope and risks of your IT project, send Admiral your resource files, target languages, and preferred deadline so the team can prepare a project-specific estimate and recommend an appropriate workflow.
