- From: Min, Hongbo <hongbo.min@intel.com>
- Date: Fri, 19 Apr 2013 12:37:49 +0000
- To: Marcos Caceres <w3c@marcosc.com>
- CC: "public-sysapps@w3.org" <public-sysapps@w3.org>
> -----Original Message----- > From: Marcos Caceres [mailto:w3c@marcosc.com] > Sent: Thursday, April 18, 2013 8:46 PM > To: Min, Hongbo > Cc: public-sysapps@w3.org > Subject: Re: Notification of availability of update. Re: Some comments in > Execution and Security Model spec > > > > On Thursday, April 18, 2013 at 2:39 AM, Min, Hongbo wrote: > > > > updated, it could send user a notification to prompt user to restart > > > the app or not when it is running. > > > There is some precedence for this. For example, Chrome on iOS > > > displays an information bar when an update is available in the App > > > Store. I don't know if it's iOS notifying the application if an > > > update is available or not, or if Chrome is doing its own checking somehow. > > > > From my experience of playing Chrome on iOS, it will have a check and notify > user that there is an available update by showing an infobar. > > Right, but is this something that should just be handled by the system (i.e., the > system can just notify the user at an appropriate time through some UI)? Or > does the application need to be notified also through a message or event? > What would be the use case for the application being notified of the availability > of an update, apart from nagging the user to update the app? > If the behavior of updating an app when it is running background is well defined, I am fine with the update notification should be handled system, not application itself since it may always nag user to update app. > > -- > Marcos Caceres > >
Received on Friday, 19 April 2013 12:38:19 UTC