Merge pull request #60 from minvws/multi-language

section on multi language support

architecture/Solution Architecture.md

@@ -43,6 +43,8 @@ The requirements document received from the Dutch health authority GGD are leadi
 - [App Considerations](#app-considerations)
   * [Native vs hybrid development](#native-vs-hybrid-development)
   * [Lifecycle Management](#lifecycle-management)
+  * [Multi language support](#Multi-language-support)
+  * [Centrally controlled app text content](#Centrally-controlled-app-text-content)
 - [GAEN protocol considerations](#gaen-protocol-considerations)
   * [Challenges to be addressed](#challenges-to-be-addressed)
   * [Proposed enhancements to the GAEN protocol](#proposed-enhancements-to-the-gaen-protocol)
@@ -361,6 +363,14 @@ Apps run on the user’s device and updates require a review process that is not
 
 * Apps should offer a ‘forced upgrade’ (i.e. if a new version is available that fixes a critical bug, it should be possible to force the user to upgrade). It is recommended that this forced upgrade can distinguish between the base operation (recording encounters) and other users, so that while we wait for the user to upgrade, they can still record their exposures.
 
+## Multi language support
+
+The Android and iOS apps support 10 languages. The translation of the texts (so-called 'copy') has been a cooperation between a translation agency and the Dutch community.
+Any textual change needs to be translated into 10 languages and then updated in a new app release.
+
+## Centrally controlled app text content
+It may be desirable for certain app texts (copy) to be controlled server-side without requiring an app update. This is e.g. one of several possible action perspectives when the user receives an exposure notification, determined by the health authority. For this, a mechanism through additional setting(s) in `AppConfig` will be implemented in the apps.
+
 # GAEN protocol considerations
 
 ## Challenges to be addressed