Software Localisation, Preparing Your App for New Markets

Software speaks to its users through words. Buttons, menus, error messages, onboarding screens and help articles all shape how people feel about a product, and when those words are in a language the user does not read comfortably, many of them simply leave. Companies that want to grow beyond their home market quickly learn that translating an app is not the same as translating a brochure. Text is hidden in code, space is limited and every release brings new strings. Software localisation works best when it is built into development from the first sprint, not added when the product is almost ready to ship. This article explains how to prepare an app or website for international users and how to avoid the most expensive mistakes.
What Localisation Includes
Localisation, often shortened to l10n, adapts a product to the language and culture of a specific market. It covers the user interface text, documentation, tutorials, marketing pages and customer support, but also date and time formats, number separators, currencies, units, sorting rules, images, colours and legal notices. The related step called internationalisation prepares the code so that all of this can change without rewriting the product. The W3C Internationalization Activity publishes practical guidance on this subject for web developers, and it is a good starting point for engineers who are new to multilingual design.
Internationalise Before You Translate
The most common source of trouble is text that is written directly into the code. Every visible string should be stored in a resource file with a clear key, so that translators can work without touching the program. Avoid building sentences from pieces, such as joining a number, a noun and a verb, since word order and plural forms differ between languages. Use proper plural rules, support right to left scripts and make sure that fonts include the required characters. Test with long words and unusual alphabets early, because fixing a broken layout is much easier before hundreds of screens exist.
Give Translators Context
A single word such as book, post or run can be a noun or a verb and may need different translations. Short strings without context are a major source of errors. Provide screenshots, descriptions and character limits for each string, and explain where the text appears and who will read it. Add notes for placeholders such as names and numbers. Glossaries that fix the translation of key product terms keep the interface consistent from the first screen to the last. When translators can see the product, they can choose natural wording instead of literal guesses.
Choose the Right Languages and Markets
Start with markets where demand is already visible, based on downloads, support requests and revenue data. Consider the size of the audience, the competition, legal requirements and the cost of support. German is often a priority for business software because of the strength of the economy, and a team that handles german translation company will know the terminology that German users expect in menus, error messages and legal texts. Add languages gradually, measure the results and expand when the process runs smoothly.
Automation, Machine Translation and Human Review
Modern workflows connect code repositories to translation platforms so that new strings are sent automatically and finished translations return as files. Machine translation can create first drafts for low risk content, such as internal tools or user generated text, while visible product copy should always be reviewed by a native speaker. Teams that already experiment with automation will find ideas in this article on AI agents for business automation, which shows how routine tasks can be streamlined. The aim is to save time on repetition while keeping people in charge of quality.
Quality Assurance in Context
Linguistic quality checks should take place inside the product, not only in spreadsheets. Reviewers need to see truncated text, overlapping buttons, wrong plural forms and untranslated strings that were hidden in the code. Create a test plan for each language, covering the main flows such as registration, payment and error handling. Use pseudo localisation, which replaces text with longer accented characters, to find layout problems before real translations arrive. Record issues in the same system that engineers use, so that language bugs are fixed like any other bug.
Support, Documentation and Marketing
A localised interface is only part of the experience. Users expect help centres, onboarding emails, store descriptions and legal pages in their language. App store listings, in particular, affect discovery, so keywords and screenshots should be adapted for each market. Prepare support teams with response templates and a path for escalating questions to speakers of the language. Consistent tone across product and marketing builds trust, and it reduces the number of tickets caused by misunderstandings.
Maintain and Improve Over Time
Localisation never ends. New features, changes in the interface and updates to laws all require fresh translations. Keep a translation memory so that repeated strings are reused, and review user feedback and ratings by language. If one market shows a lower score, check whether wording or layout is to blame. With a clear process, a prepared codebase and skilled linguists, your product can feel native in every country where it is used, and users will reward you with loyalty and recommendations.