New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove language selection from settings #1930
Comments
I have no objection if this is the convention with other apps. On the other hand, it is a differentiator for Piwik Mobile as it clear that the language can be changed independently of the phone's locale. Either way, I'm in favor of bundling the translations with the app if it improves startup times. Would it auto-update the translations if the server has a newer version? |
We currently auto-update the translations via REST api. We cache the fetched translations on the user's device until the user installes a newer version of Piwik Mobile (not server). We would auto-update the translations on each new release even if we bundling the translations with the app. I don't know any mobile apps where it is possible to change the language. I've absolutely no problem to let the language selectable. I do not think it particularly affects the start time, only the translation function would be a little bit faster. We could ask the users in the survey (whether they use/want this feature) and decide afterwards. |
I think it makes sense that the language can be changed... who knows maybe people would prefer to use piwik in english for example, rather than their native language (if the translation is not complete for example). What did you mean by "The app will be easier for the user because he does not have to worry about it." - is it currently complex for the user to pick a language? |
(In [4032]) fixes #1930 |
I think we should not make the language selectable. This has several advantages.
The app will be easier for the user because he does not have to worry about it. We can use the Titanium built-in i18n feature which should be faster. We can compile all translations into the app and do not have to query these via HTTP. The app has the correct translation from the first start on.
The i18n feature will automatically use the locale of the phone. We can assume that the user understands that language and it is not necessary to select a different language.
I think the only downside is that we have a larger app file and the user is not able to specify another language (which should not be necessary).
We could create the XML translation files automatically. See here for more details about Titanium i18n feature http://developer.appcelerator.com/guides/en/internationalization.html
Any objections?
We could use i18n as soon as we are compatible to Titanium 1.5
The text was updated successfully, but these errors were encountered: