When you add a new translation to your app...
...there is always at least one user that wants it back to English (the default language), while his device's system primary language is set to the language for which you just added the translation...
And we're talking about a professional and full translation here, not some horrible Google Translate job...
Posted Mar 2, 2020, 5:34 PM UTC
17
That's why despite being against Google "suggestions" configurable language in settings is nice to have when you deal with many translations and power users.
That's what I will end up doing. But I still do not understand why some users configure the system language of their device in their mother tongue and want (some?) apps in another language, assuming properly translated app. They could just set their device in English and have all apps in English.
I do this because I get localization and many other services based on my device language.
I prefer English but if I changed it to english I would get worse content on many other apps and google services.
So if possible please allow me to change back to english :)
Ok, that makes sense and I can understand why someone would want to do that.
Your case is a little different than mine, but as media application that displays external data, many have the external data setup in English for consistency and more data available when scrapping.
So many asked me that over the first years because having all the media data in English but the buttons in another language is not nice looking for them.
I set my device language to English, because it makes it a lot easier to follow online tutorials / instructions for how to adjust device settings. But my primary language is a different one and I'd like my apps to be in that language, at least if they are apps specific to my country like banking, public transit, weather, etc.
The case I described is the opposite: device in primary's user language and user wanting app in English (despite app having good translation in primary's user language).