- From: Janusz Majnert <j.majnert@samsung.com>
- Date: Wed, 24 Jul 2013 09:03:14 +0200
- To: public-sysapps@w3.org
On 2013-07-23 18:06, POTONNIEE Olivier wrote: > Hi > > The Runtime and Security Model specification only defines a programmatic > API to trigger installation of an application (using > ApplicationRegistry.install()). This has been discussed a bit here: https://github.com/sysapps/runtime/issues/92 > Although this model suits the packaged application model, which can only > be accessed when explicitly installed, it is less convenient for hosted > applications, that may be accessed while navigating in a browser. > Wouldn’t it be pertinent to define a way by which a UA could detect the > presence of the manifest and automatically offer the user to install the > application? This would avoid the need for the app to include a script > checking if the app is installed, and triggering installation if not. > > The Runtime and Security Model specification could define a meta tag > name (eg “sysapp-manifest-url”, or simpler “app-manifest”) that could be > inserted in any html page within the sys app origin. For instance: > > <meta name="app-manifest" > content="https://app.domain.net/path/to/manifest.webapp"> We are already workin on this. SysApps WG passed the manifest work to WebApps WG. This is being now discussed there, for example: http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0639.html > > When a UA parses such a meta tag in a page’s header, it would: > > -Check if the application is already installed or not > > -If not, prompt user to install it.. (not normative: UA will propose > “Install” or “Don’t install”, and may also offer “Never” and remember > this user choice in the browser preferences) -- Janusz Majnert Samsung R&D Institute Poland Samsung Electronics
Received on Wednesday, 24 July 2013 07:04:01 UTC