New Feature: Developer access to new update notifier

[GoogleCodeExporter]

A method to check if there is an update available, but not actually run the 
update.  This would give the developer more control of the application.  i.e. 
the dev could run a method to check if there's an update and if there is...put 
up a dialogue that advises the user and asks if they want to update or not.  or 
maybe a popup that tells them they will be updated in 10 seconds unless they 
cancel, the options are endless.  But a way for the dev to tell there's an 
update internally inside the application is very useful.

Original issue reported on code.google.com by bric...@gmail.com on 15 May 2012 at 1:05

[GoogleCodeExporter]

1. The update process is very asynchronous, it's not related in any way to the 
general application workflow and it's quite difficult to produce a working 
interaction scenario.

2. Update requests are run on timer to reduce the server load to a manageable 
value. User applications tend to ask for updates either too seldom or too often.

3. If there's an update, the end-user will be given a standard user-friendly 
notification (s)he have seen many times and knows how to ignore or dismiss, 
unlike the application modal dialog/popup.

It's possible to create a haveAnUpdate() function, which does not access the 
server, but returns True if the update is downloaded and available and, most 
probably, there's already a notification icon in the status bar telling user 
about that. But do you really need this?

Original comment by lenik.terenin on 13 Jun 2012 at 5:56

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

It would be nice if the updater sent a broadcast or called a call back when it 
was about to start the download of a  new APK... that way I can let the user 
know that a restart is about to happen. I use the silent updater.

Original comment by d...@codesushi.com on 13 Jun 2012 at 11:17

[GoogleCodeExporter]

I'm thinking about making the silent updater to "implements Observable", so it 
can be called like:

silent_aua.addObserver(this);

and then the calling class can implement "Observer" and use:

@Override
public void update(Observable observable, Object data) {
// ...
}

to get updates when something interesting happens. would this be enough?

Original comment by lenik.terenin on 16 Jun 2012 at 1:18

[GoogleCodeExporter]

Yeah,  Think that would be a help.

Original comment by d...@codesushi.com on 18 Jun 2012 at 7:53

[GoogleCodeExporter]

Please, check out the repository top.

I've added three messages, AUTOUPDATE_CHECKING is sent when we are about to 
send the request to the server, and AUTOUPDATE_NO_UPDATE / 
AUTOUPDATE_GOT_UPDATE are sent later depending on the server response.

On the contemporary broadband network it takes less than a second to download 
the update file, so the user may not have time to react. Still, it might be 
possible to save small amount of data just before the upgrade.

Original comment by lenik.terenin on 19 Jun 2012 at 4:15

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by lenik.terenin on 19 Jun 2012 at 4:16