Contents
AI translation makes apps multilingual much faster and at lower cost: UI strings, help articles, product descriptions and even chat messages between users can be translated with language models at high quality. The result only becomes dependable, though, with a well-designed workflow of glossary, context, native-speaker review and proper technical internationalisation. This article shows which content suits which approach and how to proceed.
Three Kinds of Translation in Apps
Before choosing tools, separate your content by type and risk:
| Content type | Examples | When | Recommended approach |
|---|---|---|---|
| UI strings | Buttons, menus, error messages, onboarding | During development | AI pre-translation plus review, shipped with the release |
| Editorial content | Product copy, help articles, newsletters, store listings | At publication | AI translation with glossary; spot checks or full review depending on importance |
| User-generated content | Chats, reviews, comments, support requests | In real time | Automatic on-demand translation, clearly labelled as machine-translated |
Legal texts such as terms and conditions or the privacy policy do not belong in an unreviewed AI workflow. They need expert review, since deviations can have legal consequences.
Why Language Models Complement Classic Machine Translation
Specialised translation services have delivered good results for years. Large language models add advantages that matter particularly in apps:
- Context awareness: you can explain where a string appears ("button, max. 12 characters", "push notification after order"). That prevents errors such as "Save" being rendered in German as "Retten" (rescue) instead of "Speichern".
- Tone: instructions like "casual, informal address" or "formal" are applied reliably – important for languages with formal and informal "you".
- Glossary adherence: product names and technical terms can be supplied as a list.
- Placeholders and formats: variables such as
{name}and plural rules survive with a clean prompt – but check them automatically anyway.
Limits remain: puns, marketing claims, cultural references and less common languages need human judgement. And models can add or drop content in translation too – the topic of hallucinations applies here as well.
The Translation Workflow Step by Step
- Internationalisation in code: all strings live in resource files (e.g. String Catalogs on iOS,
strings.xmlon Android, ARB files in Flutter, JSON in web apps), with no hard-coded text. Date, number and currency formats come from platform APIs. - Create a glossary and style guide: fixed terms, forbidden translations, form of address and tone – per target language.
- Provide context: every key gets a short description and, where needed, a length limit.
- Automate AI pre-translation: new or changed strings are translated automatically in the CI pipeline or translation management system.
- Automated checks: placeholders complete? Length within limits? Glossary terms respected? HTML tags intact?
- Human review: native speakers review critical strings and spot-check the rest – ideally inside the app, because context errors only show up on screen.
- Feed back corrections: fixes go into the glossary so the same mistake does not recur.
For preparing markets, payment methods and legal requirements beyond language, see our guide to internationalising your app for new markets.
Real-Time Translation of User Content
For marketplaces, community and service apps, live translation is especially attractive: a customer writes in Polish, the service agent reads German and replies in German, and the customer receives Polish. Keep in mind:
- Labelling: mark machine-translated messages as such and make the original available with a tap.
- Cost: every translation incurs model costs. Translate on demand rather than pre-emptively, and cache results. Our guide to calculating LLM API costs helps with estimates.
- Data protection: messages often contain personal data. Choose providers with EU processing, a DPA and no training on your data.
- Latency: smaller, faster models or specialised translation services suit chats best.
- Voice: combined with speech recognition, you get interpreting features, for example for field service or care.
Costs and Effort
The biggest cost item is rarely the translation itself but the technical groundwork. An app built with internationalisation from the start can add languages with little extra effort. An existing app with hard-coded strings, German date formats in the code and layouts with no room for longer words has to be refactored first – depending on scope, that can be a sub-project of its own.
Prioritise languages by market potential rather than tackling them all at once. A second language exposes most technical problems – missing string keys, tight layouts, hard-coded formats. From the third language onwards, the process becomes routine. Also plan for every new feature to ship in all languages from then on: the translation step belongs in the definition of done for each release.
AI translation of the UI strings of a typical app usually incurs only modest model costs. The real effort lies in the glossary, native-speaker review, testing on every screen size and localised store listings. If you are planning a multilingual app, our offer wizard leads to a fixed-price quote after a free analysis.
Checklist for Multilingual Apps with AI Translation
- All strings in resource files, none in code
- Layouts tolerate 30–40 % longer text and, where relevant, right-to-left languages
- Glossary and style guide per language
- Context description per string key
- Automated checks for placeholders, length and tags
- Native-speaker review for onboarding, checkout and store listings
- Legal texts reviewed by an expert
- Machine-translated user content labelled
Conclusion
AI translation significantly lowers the barrier to multilingual apps – provided the app is technically internationalised and the workflow includes glossary, context, automated checks and human review in the right places. Separate UI strings, editorial content and user content, and choose the appropriate level of review for each category.
Frequently Asked Questions
Is AI translation good enough for an app UI?
With context, a glossary and automated checks it usually provides a very good foundation for common languages. For onboarding, checkout and store listings we still recommend native-speaker review.
Can I translate terms and privacy policies with AI?
As a draft, yes – but publish legal texts only after expert review, because translation errors can have legal consequences.
How much does it cost to make an app multilingual?
Pure AI translation costs are usually low. What matters is whether the app is already internationalised; if not, the technical refactoring is the larger cost item.
Should chat messages be translated automatically?
For marketplaces and service apps it often makes sense, but translations should be labelled, keep the original accessible and run through a suitable, privacy-compliant provider.