Apk distribution implementation

content/capture-app/app-apk-distribution.md

@@ -5,7 +5,7 @@ This section focuses on the [APK Distribution Web App](https://apps.dhis2.org/ap
 
 The [APK Distribution Web App](https://apps.dhis2.org/app/dff273fc-909e-48af-b151-c4d7e9c8a12c) enables implementation administrators to manage and control the version of the Android app, making it easier to manage app updates and ensure compatibility with the DHIS2 system. 
 
-Admins will be able to upload the desired version and users will get a prompt message to update when they are not in the last updated version.
+Admins can upload the desired version to the server and mobile users will get a prompt message to update (on their first connection and every 24 hours) whenever they are not in the last updated version. More information about how to manage devices can be found in the "Distribution of the App" section of the [Android Implementation Guide](https://docs.dhis2.org/en/implement/android-implementation/scale-up.html)
 
 Please note that in this version of the Web App, only users with "ALL" authority are able to define the Android app versions. Other users having access to the web app can see the version history list and download the latest version, but cannot edit them.
 

content/capture-app/settings.md

@@ -13,7 +13,7 @@ Sync parameters
 
 > **Note** 
 >
-> Sync data, Sync configuration and Sync parameters can be overwritten using the Android Settings Web App as described [in the specific section][#capture_app_andoid_settings_webapp_synchronization]
+> Sync data, Sync configuration and Sync parameters can be overwritten using the Android Settings Web App as described [in the specific section][#capture_app_android_settings_webapp_synchronization]
 >
 >
 
@@ -45,6 +45,6 @@ SMS Settings
 :	This sections allows to check or edit the parameters related to the sms gateway.
 
 Software Update (New 2.8)
-:	This feature enables implementation administrators to manage and control the version of the Android app from the DHIS2 user web interface, making it easier to manage app updates and ensure compatibility with the DHIS2 system. Managers will be able to upload the desired version and users will get a prompt message to update when they are not in the last updated version. The management of versions is made through a new Web App.
+:	This feature enables implementation administrators to manage and control the version of the Android app from the DHIS2 user web interface, making it easier to manage app updates and ensure compatibility with the DHIS2 system. Managers will be able to upload the desired version and users will get a prompt message to update when they are not in the last updated version. The management of versions is made through the [APK Distribution Web App](#capture_app_apk_distribution_webapp)
 
-![](resources/images/capture-app-image229.png){ width=25%}
+![](resources/images/capture-app-image229.png){ width=25%}

content/implementation-guide/scale-up.md

@@ -17,7 +17,12 @@ You should consider the feasibility of using a BYOD policy - this format allows
 
 **Distribution of the app** (now and later)
 
-DHIS 2 Android app has a new release every couple of weeks. Each new release contains bug fixes and could contain new functionality. It could also contain new bugs. New versions are published in GitHub as well as Google Play store. Github is only a repository: you will download a specific APK and install it on your device. You will need to allow the use of third-party permissions to install an APK. Once an APK downloaded from GitHub or via other method, the installed version will never auto-update. On the other hand, if you install from Google Play, it normally auto-updates to the latest version. It is possible to disable auto-update in gPlay if you need to.
+DHIS2 Android app major versions are released twice per year, minor versions (which fix previous bugs and might add small new features) are released in between those major versions as needed. New versions are always published via two channels: Google Play Store and [GitHub](https://github.com/dhis2/dhis2-android-capture-app/releases/). If you install the App from the Google Play Store, it will auto-update by default with each new version (although this behaviour can be disabled).  Github is only a repository from where you can download a specific APK and install it on your device. You will need to allow the use of third-party permissions to install an APK. Once the APK is installed from GitHub or via other method it could be updated via the [APK Distribution WebApp](#capture_app_apk_distribution_webapp).
+
+> **Note**
+>
+> Whenever a new APK is added via the APK Distribution WebApp, devices connected to the server and with Internet connectivity will be asked to install the new version every 24 hours. Users can also trigger a search for updates via the Settings > Check for updates.  
+> ![](resources/images/implementation-guide-apk-update.png){ .center width=40%} ![](resources/images/implementation-guide-apk-update-manual.png){ .center width=40%}
 
 Once you complete your testing and training materials, and start your rollout, you don’t want the application version to change for any of the users, unless you have re-tested the new version. Version changes could include a modified UI, erroneous behaviours, or an incompatibility with your DHIS 2 server version. You want to thoroughly test new versions before pushing them to your users, so you can ensure that the new version doesn’t cause any problems to your configuration, requires retraining, on requires changes to your configuration.