hash13
commented
8 years ago new structur: { "appinfos": { "android": { "currentAppVersion": 91, "minimumAppVersion": 89, "downloadURL": "http://m.qabel.de/apps/android.html" } "desktop":{ "currentAppVersion": 91, "minimumAppVersion": 89, "downloadURL": "http://m.qabel.de/apps/desktop" } } }
Add function to check if app update availible.
two scenarios:
a: app inform user that a new update availible. user can accept and download new version (via google play) or click on no->app starts normaly. the app should store if user click no and app ask him no earlier than 3 days later
b: current app version is not supportet anymore (important server changes, security issues, version to old, new server urls). app tell user that the current version is no longer supported. the dialog have only a ok button. if user click on this button, the app redirect direct to google play
suggestion for server communication: e.g. to http://qabel.de/status (best case is a dedicate server/domain or a server that never overloads, e.g. qabel.prae.me/status)
header: token (optional) post: { "platform": "android", "version":"101" } the version is the version code from android manifest (not the values that displayed to user (like V1.01).
response: { "update-availible":"true|false", "update-necessary":"false|true" "server-status":100" }
The field server status is optional. With this can we code function that app can show addition informations to user, like server currently not availible and other stuff..
other codes: tbd
The request to server version should start until splash screen is showed. The timeout is set to maximum of 3 seconds. If no response from server, the app starts normaly without this check (e.g. no net access).