[Sparkle] Proposed solution

[Steven W Riggins]

On Aug 6, 2007, at 2:21 AM, Andy Matuschak wrote:

> You're absolutely right. It's not quite so bad, since it'd only be  
> one time instead of once for every app, but it's disruptive, and it  
> sucks. How about asking the user on the second launch? I don't  
> think that'd be quite so bad. They like the app; they've come back  
> to it. The first impression has already been made. This is what  
> Panic does.
>

How about checking for a new version of the app.  If there is none,  
ask the user on QUIT.  If there is a new version, ask them on  
LAUNCH.  That way they have a chance to get up to date.

Scenario I am thinking of:

Do a clean and install of a NEW OS on an existing machine.  Run a app  
I have not run in eight months.  It likely has a new version to  
utiliize the new OS.  I'd like to know before I ran it.

Other cases, I just downloaded the latest app, I don't want to be  
bugged, but when I quit, ok, cool!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andymatuschak.org/private.cgi/sparkle-andymatuschak.org/attachments/20070806/e3644942/attachment.htm