Most Recent

Latest In Tech

A software team decides to launch in another market. Someone exports the interface text, sends it for translation and adds a language option to the settings menu. On paper, the job looks almost finished. The first review tells a different story. Several buttons are too narrow for their new labels. An error message has no clear meaning outside the screen where it appears. The welcome email still arrives in English, and the help centre describes a feature using a different name from the app. None of these problems is especially surprising once you see it. They are simply difficult to catch when translation is handled separately from product development. For teams preparing their first multilingual release, the challenge is deciding what to include, giving translators enough context and leaving time to test the result. A workable process starts well before the final text is ready. Choose a Specific Audience and a Manageable First Release “Make the app available internationally” is too broad to guide a project. Choose the market you want to serve and identify what users there should be able to do.…

Today's Picks

Culture

Digital Classics

A software team decides to launch in another market. Someone exports the interface text, sends it for translation and adds a language option to the settings menu. On paper, the job looks almost finished. The first review tells a different story. Several buttons are too narrow for their new labels. An error message has no clear meaning outside the screen where it appears. The welcome email still arrives in English, and the help centre describes a feature using a different name from the app. None of these problems is especially surprising once you see it. They are simply difficult to catch when translation is handled separately from product development. For teams preparing their first multilingual release, the challenge is deciding what to include, giving translators enough context and leaving time to test the result. A workable process starts well before the final text is ready. Choose a Specific Audience and a Manageable First Release “Make the app available internationally” is too broad to guide a project. Choose the market you want to serve and identify what users there should be able to do. For a scheduling tool, the first release might cover creating an account, setting availability, booking an appointment and receiving reminders. Reporting features used by a small number of administrators could follow later, provided those limits are made clear. This approach gives the team a complete journey to work on. It also makes testing more meaningful: reviewers can check whether someone can finish an ordinary task without encountering unexplained language changes. Look at existing demand when setting priorities. Enquiries from prospective customers, requests from a distribution partner and feedback from current users can all help establish where to begin. Make sure the business can support the chosen market. A translated interface creates expectations about onboarding, billing and help after purchase. Those arrangements should be considered alongside the product work. Find the Text Outside the Main Interface The visible screens are only part of the content inventory. Software also communicates through notification emails, password resets, downloadable reports, payment messages and instructions supplied by outside services. Some of that wording may live in systems the product team rarely opens.…