An app’s ability to generate revenue is driven in large part by the way it’s presented to users in different countries. The RadASO team shares some insights on the peculiarities of displaying the app’s name, description, and screenshots based on the user’s location. Save this handy cheat sheet!
Discuss Metadata Adaptation with Other ASO Experts on Discord.
Localization is a variation of an app’s page in the App Store that is shown to users in a particular country. Each locale has its own set of textual and graphic metadata (name, description, and screenshots). These data are added via the developer’s console App Store Connect, which is used for app management.
.webp)
At the time of writing, App Store Connect allowed to add up to 39 locales.
Each country may have 1 to 10 active locales. For instance, the UK has two locales – English (U.K.) and English (U.S.) while the USA has ten locales – English (U.S.), Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico), and Vietnamese. For the complete list of locales available for the particular country, refer to Apple’s help.
1. The user’s country, as specified in their Apple ID account.
2. Default language and additional supported language or that country. This info is available from the localization coverage table.
.webp)
3. Language set on the user’s device.
4. Locales that are added for the app in the App Store Connect.
5. The app’s Primary localization in the App Store Connect.
App: Belote.
Added localizations: English (U.K.), French, Ukrainian, Spanish (Mexico).
Primary localization: English (U.K.).
1. The user sees metadata in the Default language for France – French, as the device’s settings only allow two languages: French and Ukrainian (not supported).
2. The user sees metadata in the Additional supported language for France– English (U.K.), as English is chosen in the device’s settings.The user sees metadata from the app’s Primary localization – English (U.K.), as the device’s Default language for Portugal is Portuguese, and the Additional supported language for Poland is Polish, neither of which is added to App Store Connect. The subtitle, in this case, is not shown.
3. The user sees metadata from the app’s Primary localization – English (U.K.), as the device’s Default language for Portugal is Portuguese, and the Additional supported language for Poland is Polish, neither of which is added to App Store Connect. The subtitle, in this case, is not shown.
Important note: Once you add one of the language variations to App Store Connect, you will automatically get its metadata for other locales of the same language that have yet to be added. Here is the list of such locales:
1. English (U.S.) ↔︎ English (U.K.) ↔︎ English (Australia) ↔︎ English (Canada).
2. Portuguese (Portugal) ↔︎ Portuguese (Brazil).
3. French (France) ↔︎ French (Canada).
4. Spanish (Spain) ↔︎ Spanish (Mexico) ↔︎ Catalan.
For instance, there are no English (Canada), French (Canada), Spanish (Spain) and Catalan in the App Store Connect. However, it does have other locales mentioned above that will be shown instead of the missing ones.
In Google Play, the app can also have multiple page variations with textual and graphical metadata that are shown to users in different countries.
At the time of writing, the Google Play Console tool allows adding over 80 translations for the app’s main page.
The complete list is available on Google Play Help. Unlike the App Store, Google Play doesn’t limit access to any languages for a particular country.
Users will see auto-translated short descriptions and full descriptions with the auto-translation switcher.
App: lalafo.
Localizations added to the app’s main page: English (U.S.), russian, and Ukrainian.
Default language:russian.
Localizations added to the store listing targeted at Ukraine: Ukrainian (Default).
1. The user sees metadata in English (U.S.), as their device is set to English (U.S.):
Note. If a localization only has textual metadata, graphical metadata will be displayed in a language set by default.
2. The user sees metadata in the Default language – russian, as their device is set to the language that has not been added to the app’s main page – French. The following parameters will be displayed:
3. The user sees Ukrainian metadata from the Custom store listing targeted for Ukraine, as the device is set to that language and the user is located in that country:
4. The user sees the Default language metadata from the Custom store listing, targeted for Ukraine – Ukrainian, as the device is set in a language different from the one added to the Custom store listing, and the user is located in Ukraine.
In that case, the user won’t see the auto-translated short description and the switcher for translation of the full description. This is why adding more languages to the Custom store listings is critically important so that users can see metadata in accordance with their device’s settings.
Important Note. Google Play also has its specifics. After adding one language variation, one will have its metadata shown for other variations yet to be added. The RadASO team’s experience allows for defining this language list:
1. English (U.S.) ↔︎ English (U.K.) ↔︎ English (Australia) ↔︎ English (Canada). English (Australia) ↔︎ English (Canada) ↔︎ English (India) ↔︎ English (Singapore) ↔︎ English (United Kingdom) ↔︎ English (United States) ↔︎ English (South Africa).
2. French ↔︎ French (Canada).
3. Portuguese (Brazil) ↔︎ Portuguese (Portugal).
4. Spanish (Latin America) ↔︎ Spanish (Spain) ↔︎ Spanish (United States).
5. Indonesian → Malay ↔︎ Malay (Malaysia).
6. German → Romansh.
7. Norwegian → Danish.
8. Czech → Slovak.
9. Chinese (Traditional) → Chinese (Hong Kong).
Therefore, it is critical to carefully plan the app’s localization in the app stores, taking into account all the aspects of metadata displayed in different countries. This will help ensure more efficient app representation, and improve conversion rate and user engagement, which will result in revenue increase.
.png)
