Skip to content

Most visited

Recently visited

navigation

Localization checklist

By localizing you can take advantage of Google Play’s worldwide reach and maximize your app’s distribution potential.

Localization involves tasks throughout your app development cycle, and planning is essential. This checklist identifies the key aspects of localization needed to get your app ready for successful local launches on Google Play.

Checklist

  • Research target languages and locales. Identify countries where there is a good market opportunity and where you can provide appropriate user support.
  • Use Google Play data to find localization opportunities. If your app is live, use the user acquisition performance report in the Play Console to identify countries where you haven’t localized but are seeing many visits to the Play Store. These visits could indicate interest in your app in that country and an opportunity to increase installs by localizing.
  • Design your app for localization. Use a single set of flexible layouts with alternative layouts where needed. Support right-to-left text, use system-provided formats for dates, times, numbers, and currencies, and include a full set of default resources.
  • Optimize your app if you’re targeting emerging markets. Review the Building for Billions best practices on how to optimize Android apps for low- and no-bandwidth connectivity and low-cost devices.
  • Manage your app’s UI strings. To prepare for translation move all strings into strings.xml, follow the Material Design guidelines on writing style, provide sufficient context information for declared strings, and mark content that should not be translated.
  • Translate your app, store listing, and other resources. Solicit translations from your users, find a translation agency yourself, or use the app translation service from the Google Play Console or Android Studio to request a reliable and efficient translation.
  • Test your localized app. Make sure you can test on the makes and models common in the markets you’re targeting. Check the UI thoroughly for formatting and presentation issues and where possible get native speakers to review.
  • Run a beta test. Plan a beta release in key countries before launch to get real-world feedback from users.
  • Plan for international marketing. Prepare to run an app install campaign and other regional or country-specific marketing from launch. Use the Google Play badge generator to build localized badges that you can use on websites or marketing materials. Generate new device art for promotional material with screenshots from your new localization.
  • Check your Optimization Tips. Check whether you’re missing parts of your localized store listing and get other helpful reminders for a successful localized launch. Launch the Play Console.
  • Final checks and publishing. First, go back and double check you’ve done everything in this list. Now you’re ready to launch or promote your app in your target country.
  • Support international users after launch. At a minimum watch your ratings, reviews, and download stats carefully to find issues that could affect users. Consider creating language specific user groups or forums, if manageable.
  • Browse and reply to user reviews. Understand what users think of your app and reply to their reviews to address any issues you might not have spotted in testing.
  • Run store listing experiments. When visits to your store listing from your new markets start growing, run a localized store listing experiment to see what text and graphics work best. You can run up to 5 at the same time.
This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields

Hooray!

Follow Google Developers on WeChat

Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience.
(Sep 2017 survey)