Most applications require only some light internationalization. This often means internationalizing string resources only, but other resources, such as layouts and graphics, remain the same for all languages and locales.
Some of the pros of this strategy are the following:
► Modest development and testing requirements
► Streamlined application size (specialized resources kept to a minimum)
Some of the cons of this strategy are the following:
► Application may still be too generic for certain types of applications. Overall design (especially screen design) may suffer from needing to support multiple target languages. For example, text fields might need to be large enough to support verbose languages such as German but look odd and waste valuable screen real estate in less verbose languages.
► Because you've headed down the road of providing language-specific resources, your users are more likely to expect other languages you haven't supported. In other words, you're more likely to start getting requests for your app to support more languages if you've supported some. That said, you've already built and tested your application on a variety of languages, so adding new ones should be straightforward.
Was this article helpful?