Content
View differences
Updated by Niels Lindenthal about 2 years ago
**As** a mobile app user
**I want the** translations in the app to be consistent with the translations in the web interface
**so that** I get easily map the concepts between both worlds.
**Acceptance criteria**
* By default the apps uses the language settings defined on the mobile device.
* If this language does not exist The translations are pulled from Crowd-in as part of the fallback is English
* We use the same translation strings we use for the web application
* [https://github.com/opf/openproject/tree/dev/config/locales/crowdin](https://github.com/opf/openproject/tree/dev/config/locales/crowdin)
* [https://crowdin.com/project/openproject](https://crowdin.com/project/openproject) build process.
https://crowdin.com/project/openproject
**Out of scope for the spike**
* Having a setting in the app to change the language.
**I want the** translations in the app to be consistent with the translations in the web interface
**so that** I get easily map the concepts between both worlds.
**Acceptance criteria**
* By default the apps uses the language settings defined on the mobile device.
* If this language does not exist
* We use the same translation strings we use for the web application
* [https://github.com/opf/openproject/tree/dev/config/locales/crowdin](https://github.com/opf/openproject/tree/dev/config/locales/crowdin)
* [https://crowdin.com/project/openproject](https://crowdin.com/project/openproject)
https://crowdin.com/project/openproject
**Out of scope for the spike**
* Having a setting in the app to change the language.