{"id":6435,"date":"2013-01-13T00:00:00","date_gmt":"2013-01-13T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2013\/01\/13\/localization-services-for-android-mobile-applications\/"},"modified":"2021-01-05T12:17:32","modified_gmt":"2021-01-05T12:17:32","slug":"localization-services-for-android-mobile-applications","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2013\/01\/13\/localization-services-for-android-mobile-applications\/","title":{"rendered":"Localization Services for Android Mobile Applications"},"content":{"rendered":"

Consumers are using all channels available to them to interact and engage with your brand whether it be via mobile, website, email, social, brick and mortar-you name it. Marketers know they cannot risk neglecting any one channel or they might miss an opportunity.<\/p>\n

“Android has been one of the primary growth engines of the smartphone market since it was launched in 2008,” said\u00a0Ramon Llamas<\/a>, research manager,\u00a0Mobile Phones<\/a> at IDC. “In every year since then, Android has effectively outpaced the market and taken market share from the competition. In addition, the combination of smartphone vendors, mobile operators, and end-users who have embraced Android has driven shipment volumes higher. Even today, more vendors are introducing their first Android-powered smartphones to market.”<\/p>\n

\"android-localization\"<\/p>\n

Top Six Smartphone Mobile Operating Systems, Shipments, and Market Share, Q3 2012 (Preliminary) (Units in Millions)<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Operating System<\/strong><\/td>\n\n

3Q12 Shipment Volumes<\/strong><\/p>\n<\/td>\n

\n

3Q12 Market Share<\/strong><\/p>\n<\/td>\n

\n

3Q11 Shipment Volumes<\/strong><\/p>\n<\/td>\n

\n

3Q11 Market Share<\/strong><\/p>\n<\/td>\n

\n

Year Over Year Change<\/strong><\/p>\n<\/td>\n<\/tr>\n

Android<\/td>\n\n

136.0<\/p>\n<\/td>\n

\n

75.0%<\/p>\n<\/td>\n

\n

71.0<\/p>\n<\/td>\n

\n

57.5%<\/p>\n<\/td>\n

\n

91.5%<\/p>\n<\/td>\n<\/tr>\n

iOS<\/td>\n\n

26.9<\/p>\n<\/td>\n

\n

14.9%<\/p>\n<\/td>\n

\n

17.1<\/p>\n<\/td>\n

\n

13.8%<\/p>\n<\/td>\n

\n

57.3%<\/p>\n<\/td>\n<\/tr>\n

BlackBerry<\/td>\n\n

7.7<\/p>\n<\/td>\n

\n

4.3%<\/p>\n<\/td>\n

\n

11.8<\/p>\n<\/td>\n

\n

9.5%<\/p>\n<\/td>\n

\n

-34.7%<\/p>\n<\/td>\n<\/tr>\n

Symbian<\/td>\n\n

4.1<\/p>\n<\/td>\n

\n

2.3%<\/p>\n<\/td>\n

\n

18.1<\/p>\n<\/td>\n

\n

14.6%<\/p>\n<\/td>\n

\n

-77.3%<\/p>\n<\/td>\n<\/tr>\n

Windows Phone 7\/ Windows Mobile<\/td>\n\n

3.6<\/p>\n<\/td>\n

\n

2.0%<\/p>\n<\/td>\n

\n

1.5<\/p>\n<\/td>\n

\n

1.2%<\/p>\n<\/td>\n

\n

140.0%<\/p>\n<\/td>\n<\/tr>\n

Linux<\/td>\n\n

2.8<\/p>\n<\/td>\n

\n

1.5%<\/p>\n<\/td>\n

\n

4.1<\/p>\n<\/td>\n

\n

3.3%<\/p>\n<\/td>\n

\n

-31.7%<\/p>\n<\/td>\n<\/tr>\n

Others<\/td>\n\n

0.0<\/p>\n<\/td>\n

\n

0.0%<\/p>\n<\/td>\n

\n

0.1<\/p>\n<\/td>\n

\n

0.1%<\/p>\n<\/td>\n

\n

-100.0%<\/p>\n<\/td>\n<\/tr>\n

Totals<\/td>\n\n

181.1<\/p>\n<\/td>\n

\n

100.0%<\/p>\n<\/td>\n

\n

123.7<\/p>\n<\/td>\n

\n

100.0%<\/p>\n<\/td>\n

\n

46.4%<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Source: https:\/\/www.idc.com<\/a><\/p>\n

Android was designed to run a wider number of varying devices in many different regions globally. This blog describes some best practices to consider when localizing and managing multi-language applications to help engage with your users in different locales on the Android platform.<\/p>\n

Understanding Application Resources<\/h4>\n

Application resource files are data files (e.g. images, audio and video) used by your application. When you create a localized application, you also create one or more resource files that contain resources localized for specific cultures and locales. You can deploy these resources within your application to target one or more cultures. Additionally, Android can select and load resources from different directories, based on the current device configuration and locale.<\/p>\n

Globalization in the context of application development provides support for localized user interfaces and data for users in multiple cultures. The term, “globally aware application” refers to an application which was been built to present its data using the locale-sensitive symbols (e.g. currency, decimal symbols, etc.) and formats which may be applicable to the given culture.<\/p>\n

Software development practices encourage approaches which yield high maintainability and re-use. Application resources files (e.g. images, sprites, layouts and static strings) should be externalized from your source code. This helps development teams to easily maintain them independently and consistently (i.e. leverage build automation tools, etc.)<\/p>\n

Supporting Multiple Languages with Application Resources<\/h4>\n

It’s always a good practice to extract UI strings from your application source code and keep them in an external file.<\/p>\n

To support multiple languages, you must provide additional resources for each of the target languages. You should place each type of resource in a specific subdirectory of your project’s resources (i.e. “res\/”) directory. Once you’ve decided on the languages (e.g. Three languages – English, Spanish and French) you will support, create the resource subdirectories and string\/image resource files. For example:<\/p>\n

MySuperSecretAndroidProject\/
\nres\/drawable-hdpi\/
\nbackground.png
\ndrawable-es-hdpi\/
\nbackground.png
\ndrawable-fr-hdpi\/
\nbackground.png
\nvalues\/
\nstrings.xml
\nvalues-es\/
\nstrings.xml
\nvalues-fr\/
\nstrings.xml<\/em><\/p>\n

Strings<\/h4>\n\n\n\n\n\n\n
Language string.xml<\/strong><\/td>\nDestination within project<\/strong><\/td>\n<\/td>\n<\/tr>\n
English<\/strong><\/td>\nres\/values\/string.xml<\/td>\n<?xml version=”1.0″ encoding=”utf-8″?>
\n<resources>
\n<string name=”title”>My Super-Secret Application<\/string>
\n<\/resources><\/em><\/td>\n<\/tr>\n
Spanish<\/strong><\/td>\nres\/values-es\/string.xml<\/td>\n<?xml version=”1.0″ encoding=”utf-8″?>
\n<resources>
\n<string name=”title”> Mi Aplicaci\u00f3n Secret<\/string>
\n<\/resources><\/em><\/td>\n<\/tr>\n
French<\/strong><\/td>\nres\/values-fr\/string.xml<\/td>\n<?xml version=”1.0″ encoding=”utf-8″?>
\n<resources>
\n<string name=”title”> Mon secret application<\/string>
\n<\/resources><\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Images<\/h4>\n\n\n\n\n\n\n
Language background.png<\/strong><\/td>\nDestination within project<\/strong><\/td>\n<\/tr>\n
English (default locale)<\/strong><\/td>\nres\/drawable-hdpi\/background.png<\/td>\n<\/tr>\n
Spanish<\/strong><\/td>\nres\/drawable-es-hdpi\/background.png<\/td>\n<\/tr>\n
French<\/strong><\/td>\nres\/drawable-fr-hdpi\/background.png<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

At runtime, the Android system<\/a> uses the appropriate set of string resources based on the locale currently set for the user’s device.<\/p>\n

Using the Localized Resources<\/h4>\n

Once you externalize your application resources, you can access them using resource IDs that are generated in your project’s R class.<\/p>\n

Therefore within your source code, you can reference a string resource with the syntax R.string.<string_name><\/em>.<\/p>\n

For example:<\/p>\n

<\/code><\/p>\n

\/\/ Get a string resource from your app’s Resources
\nString title = getResources().getString(R.string.title);<\/em><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Consumers are using all channels available to them to interact and engage with your brand whether it be via mobile, website, email, social, brick and mortar-you name it. Marketers know they cannot risk neglecting any one channel or they might miss an opportunity. “Android has been one of the primary growth engines of the smartphone […]<\/p>\n","protected":false},"author":3,"featured_media":6436,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[1269,1425,1464],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6435"}],"collection":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=6435"}],"version-history":[{"count":5,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6435\/revisions"}],"predecessor-version":[{"id":22472,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6435\/revisions\/22472"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/6436"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=6435"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=6435"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=6435"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}