Segmentation & Content Personalization: Auto Language Support
In a multi-cultural and multi-regional global marketplace, it’s crucial for apps to be able to support language localization. And, by extension, your push notifications should too. Your app should offer a feature in settings where users can select which language they want to experience the app in. Then, push notifications should be able to either align with the app language or automatically revert to the default language of the user’s device. OpenBack offers complete auto language support, and you can add as many languages as you want on our dashboard.
Download our NEW Metrics & Measurement Playbook to learn how to optimize your push campaign!
Why Should You Localize Your App and Notifications?
App and push notification localization is important so you can communicate with users who speak different languages. This offers benefits on many different levels. Primarily, it’s key for any app that aspires to expand to the global market. One need only look at the delayed rollout of the Pokemon GO app. By only being available in the US, Australia, and New Zealand at first, this resulted in copycat apps and illegal downloading in the rest of the world.
While English is the most spoken language on the planet at 1.35 billion, it’s important to meet international users on their own ground. Even in the US market, there are over 40 million Spanish speakers, over 3 million Chinese speakers, and so on. If your app isn’t catering to a multilingual user base, you’re missing out on a crucial and lucrative market.
Likewise, push notifications as extensions of your app experience need to have multi-language capabilities. To have a disconnect between the device language and the language of your push notifications makes for a clunky UX as a whole. Using multiple languages for notifications can help boost engagement with your app as well.
How to Localize Your Push Notifications With OpenBack’s Auto Language Support
OpenBack offers complete multi-language auto support. Our hybrid platform uses mobile edge computing to leverage user data on-device, meaning you can automatically align your push notifications to the language in which individual user devices are configured. You can do this by accessing the OpenBack dashboard, where for a particular push campaign you then assign the language of your notifications to be the user’s device default language. Following this, you then enter the desired content of your notification into the dashboard. (Note: it’s important to invest in a professional translator to write your content… Google Translate is not a reliable source, and poor translations can result in unpleasant misunderstandings!)
Even if your app only offers limited languages, OpenBack is compatible with all languages. So if, for example, your mobile game only comes in English and Mandarin, OpenBack will be able to detect that a user’s device is set to Cantonese, and you will be able to deliver localized notifications and in-app messages in Cantonese.
Notification Localization for iOS and Android
Android and iOS devices both have localization UI and features to assist your app in structuring its code. For Apple, there is XCode 11, Apple APIs, Auto Layout, and Unicode. With this suite of tools, developers can better address varying design and layout aspects of languages that differ from English. For example, Hebrew and read left to right, while Mandarin and Japanese read vertically, and so on. Auto Adjust then enables developers to adjust text layout and dimensions. iOS 13 and iPadOS 13 moreover gives users full control over what language they experience individual apps in, no matter what language they have their device set to.
As for Android, it offers developers the capability to use Java to create various default resources to localize your mobile app:
Put the app’s default text in
The text strings in
res/values/strings.xmlshould use the default language, which is the language that you expect most of your app’s users to speak.
The default resource set must also include any default drawables and layouts, and can include other types of resources such as animations:
res/drawable/(required directory holding at least one graphic file, for the app’s icon on Google Play)
res/layout/(required directory holding an XML file that defines the default layout)
res/anim/(required if you have any
res/xml/(required if you have any
res/raw/(required if you have any