In Part 1 of this two part post, we looked at the basics of international software, and how to plan your project to best support the demands of international applications. In this second post, we look at using local market knowledge to speed up localisation efforts, the pros and cons of a translation management system, and some ways to avoid mobile app "sprawl".

Web and mobile applications today should be designed and built from the ground up to support international markets, unless there is a strong business case to restrict them to a single market. The availability of tools and frameworks to provide your application with international support (including multiple languages, currencies, locales, etc.) lowers the barrier for application development teams, but the technology build is only part of the challenge of supporting international markets. In Part 1 of this two part post, we look at the basics if international software, and how to plan your project to best support the demands of international applications.

When budgets are limited, web product owners can face a daunting task of deciding which SmartPhone device to support first. With market share changing so rapidly, this can be a difficult decision. We've pulled together some statistics on SmartPhone use to help with these kinds of choices.