Contents
In today's global marketplace, delivering high-quality software across different languages is key. And shifting left can help to achieve this. The concept is not new. Many companies already shift left in their traditional software cycle. The teams collaborate early in the process, at the initial stages of coding, to catch issues sooner and to ensure a sound final product. Wouldn’t it be great if we could use this in localization as well? If we could integrate internationalization (i18n) and localizability considerations early in the dev process, from the design stage through implementation, we could go from GIGO to QIQO (quality in, quality out), improving localization output and the experience for end users. In this talk, we will look at 3 “magic” ingredients to maximize the value-add of localization in creating multilingual software. We will explore how design-stage localization, internationalization, and UX writing as pre-localization steps can lead to a more efficient localization practice and an enhanced global user experience. We will look at examples of right and wrong ways to do this, and we will dig into why this approach hasn’t become a best practice yet.
Takeaways
Join us in this session for insights on: -Shifting left: what it is, how it serves us in the context of localization, and how incorporating the three magic ingredients can up the quality of your UI localization recipe - From zero to hero: why some companies do it better than others - The good, the bad, and the ugly: examples of poor and best practices