18.1. The need for localization

For many programmers there’s only one language: Java. Of course the world is larger than one programming language, and it’s much larger than a single spoken and written language. The majority of computer users choose a language when they set up their computer and never think twice about the decision. In fact, after the initial setup many of the resources related to other languages may even be deleted from the computer or phone, to save storage space. If this describes your experience, you’re not alone! The aim of this chapter is to equip you to navigate the task of localizing an Android application and in the process reach a broader audience. As a side benefit, you’ll likely find that you look at application development differently, even if you never pursue localization of your own applications.

The reasons for localizing an application are manifold. For a commercial application, there are numerous markets to reach; there’s no need to limit your sales to a single marketplace. Your application may be bound for some cultural reasons to a specific region, but many applications such as games, utilities, and productivity tools are of universal interest and appeal. Games in particular are often relatively light in textual components, with the majority of the text constrained to settings screens and help files. It’s to the developer’s advantage to access additional markets to increase sales volume. Volume is important, considering the low price point of most mobile applications.