On Sun, Sep 16, 2012 at 3:40 PM, Ian Bicking <[email protected]> wrote: > On Fri, Sep 14, 2012 at 3:28 PM, Matt Claypotch <[email protected]> wrote: >> >> In developing app testing tools, we frequently want a discovery >> mechanism to let a page point to its manifest. Given that we presently >> don't have a required known path to an app's manifest, I'd like to >> propose we formalize an *optional* <link> tag that a website can use >> to indicate it is an app. >> >> I made up a sample tag on the fly for an apps hackathon shim [1]. It >> looks like this: >> >> <link rel="app-manifest" href="manifest.webapp"> >> >> Use cases for this include: >> >> - Visiting the website of an app in the Gaia browser can offer to >> install the site as an app > > > Would it make more sense to link to the preferred store page for > installation, instead of directly to the manifest? Even for unpaid apps > there seems to be some features where we'd encourage people to go through a > store, since the store may in effect vouch for the app with respect to some > permissions.
Google has a <link> for the Chrome Web Store, and I believe that standardizing metadata for "here's where to buy this" has its place, but this proposal is targeted toward in-development or standalone OWAs in addition to ones listed in a marketplace, so that would ideally be a separate effort. > > -- Matt "potch" Claypotch "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
