Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App planning · 17 Nov 2026 · 5 min read

App localisation: translating an app for new markets

Translation is the visible part. Localisation also changes dates, numbers, layouts, store pages and support, and it is much cheaper to plan before the first screen is built.

The short answer

App localisation adapts an app to a language and region: translated text, but also date, number and currency formats, plural rules, text direction, images, legal wording and store listings. Plan for text that grows or shrinks, keep all strings out of the code, and test each language on real devices with a native speaker.

App localisation is more than translated words

App localisation means making an app feel native in a given language and region. Translation is the biggest part, but it is only one part. A user in a new market also notices how dates are written, which way the text runs, whether names fit the sign-up form and whether the payment options look familiar.

The distinction matters for budgeting and scheduling. A translator can finish a spreadsheet of strings in days, yet the app may still be unusable in that language because buttons overflow, the date picker is wrong or the store listing is still in English. Localisation is a product task shared between design, development, content and support.

What localisation includes beyond translation

  • Dates, times and calendars. Order of day and month, 12 or 24 hour clocks and the first day of the week differ by region.
  • Numbers and currency. Decimal and thousands separators vary, and currency symbols may come before or after the amount.
  • Units. Distances, weights and temperatures are shown differently in different places.
  • Plural rules. Some languages have more than one plural form, so a simple one item or many items switch is not enough.
  • Text direction. Languages written right to left need a mirrored layout, not just translated words.
  • Names and addresses. A form that insists on a first name, a last name and a state will frustrate many users.
  • Images and icons. Pictures with text baked in must be redrawn, and some symbols or gestures carry different meanings in different places.
  • Legal and policy text. Privacy notices, terms and consent wording may need local review by a qualified person, because rules differ by country.
  • Payment methods and support. Users may expect other payment options and support in their own language.

How to plan text that grows or shrinks

Text length changes with language. Some languages need noticeably more characters than English for the same message, and others need fewer. Labels that look balanced in English may truncate, wrap or push other items off screen elsewhere.

Design for that from the start rather than fixing it screen by screen later:

  • Use flexible layouts that let text wrap and containers grow, instead of fixed widths for labels and buttons.
  • Give buttons room, and avoid designs where one word sits snugly in a small pill.
  • Never build a sentence by joining separate pieces of text in code. Word order differs between languages, so each full sentence, with its placeholders, should be one translatable string.
  • Avoid text inside images and icons.
  • Allow for user font size settings, which can multiply the effect of longer words.

A useful trick is pseudo-localisation. The build swaps every string for a longer, accented version of itself. Overflowing text and hard-coded strings then show up in the first week of development, long before any translator is involved.

Prepare the code and content

The developer's side of this is mostly discipline. All user-facing text lives in resource files that the platform's localisation system reads, not in the code. Dates, numbers and currency are formatted with the system's own tools, which already know regional conventions. Placeholders are named, so a translator can reorder them.

Content that arrives from a server needs the same thought. If product names, notifications or help articles come from your system, then the system must store and serve them per language. The guide to what an app backend does explains why, and why a missing translation should fall back to a sensible default instead of an empty field.

Decide early who writes the first draft. Machine translation can give a quick starting point, but a person who speaks the language should read every screen before release, especially for tone, politeness levels and anything legal or financial.

Choose which markets to add first

Adding a language adds a recurring cost: each release brings new strings, and each language needs review, testing and support. Pick markets using evidence rather than ambition. Existing usage, support requests from non-English speakers, store search data and partner demand are all better signals than a hunch.

Your analytics can help, provided they record the device language and region. See what to track in app analytics for how to set up that kind of measurement. Add one market first, learn from it, then repeat the process for the next.

Money, notifications and other moving parts

Some features need extra attention in each market. Subscription and purchase prices are set per region in the stores, so check how your product list is configured, and read in-app purchases and subscriptions basics for the structure. Tax rules differ by country, so check them with a qualified adviser and the store's current documentation.

Push messages need their own translated copy and sensible send times for each time zone. If you are weighing that up, the guide to when and how to use push notifications covers frequency and relevance. Support replies, help articles and email receipts also need a language plan, even if the answer is that English-only support is stated clearly in the app.

How to test each language

Test every added language on real devices, not just in a simulator, and give each one its own pass.

  1. Run the pseudo-localised build first to catch truncation and hard-coded text.
  2. Have a native speaker walk through the main journeys in context. Reviewing a spreadsheet of strings is not the same as seeing them on screen.
  3. Check the device language and the region setting separately. A user may have an English phone set to a different region, and the app should handle that sensibly.
  4. Test dates, numbers, currency and sorting with real examples from that market.
  5. Test right-to-left layouts on every screen, including keyboard and icon direction, where relevant.
  6. Check notifications, emails and receipts as well as screens.
  7. Take store screenshots in each language, because the listing is part of the product.

After release, watch for problems that only show up in one language. Segmenting your crash data by locale is a quick way to spot a layout that fails only on long strings; see what to set up first for crash reporting and analytics.

Keep localisation going after launch

Localisation is never finished. Every new feature adds strings, and a late change in English can leave other languages stale. Build the habit of marking strings as new or changed, sending them for translation at a set point in each release, and holding the release if a language is incomplete.

If you want help planning this alongside the technical build, the mobile app development page describes what Liftup Technologies offers for apps.

Related guides

Questions and answers

What does app localisation include beyond translation?

It also covers date, number and currency formats, units, plural rules, text direction, names and address forms, images with text, legal wording, payment options, support and the store listing. A translated app that ignores these can still feel foreign or break layouts.

How do I plan text that grows or shrinks in other languages?

Use flexible layouts, avoid fixed-width labels, keep every full sentence as one string, and avoid text inside images. Pseudo-localisation, which swaps text for longer accented strings, shows overflow problems early in development.

How do I test each language in an app?

Run a pseudo-localised build first, then have a native speaker use the app in context on a real device. Check the device language and region separately, and test dates, numbers, currency, notifications, emails and store screenshots too.

Can I use machine translation for my app?

It can produce a first draft quickly, but a person who speaks the language should review every screen, especially for tone and for legal or financial wording. Treat machine output as a starting point, not a finished translation.

Which language should I add first?

Use evidence: where your current users are, support requests in other languages, store search data and partner demand. Add one market first, learn what it costs to maintain, then decide on the next.

Do I need to translate the store listing as well?

Usually yes, if you want people in that market to find and trust the app. The title, descriptions and screenshots are part of what users see before installing. Each store lets you add listing text per language.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote