"Unfettered" Android-Based Mobile Application Update Suggestions
Summary
Due to removal of the percentage-based visual feedback for the "unfettered" Android-based mobile application (re: #5331 (closed)), there is no longer any form of feedback to provide information about if the application has failed to update and due to this point, I have come up with the following suggestions.
a. Implement some form of visual representation for the transferral of data which results in the update (I am thinking on the lines of the "egg timer" progress-based concept that is generally used within operating systems / desktop environments).
b. Implement a timeout-styled concept, in which after a set amount of time (I am thinking around fifteen minutes) during the progress routine, the application either retries to update or provides an error message.
c. Implement a manual update-based function that is accessible from within the "settings" / "other" / "app" section to act as a form of fallback-based mechanism.
I came across an issue when initially updating the application from version 4.41.1 to version 5.0.1, which caused the update routine to seemly stall (I waited approximately thirty minutes to see if the update would succeed, which it did not) but on the second attempt, the application updated within a couple minutes (I am presuming that the failure of the first attempt was related to localised infrastructure-based issues) and I am thinking that the above three suggestions would aid in combating any unsuccessful updates.