Contact: Mounir Lamouri <
mlam...@chromium.org>
Spec:
http://w3c.github.io/manifest/
Summary:
To quote the specification:
"This specification defines a JSON-based manifest, which provides
developers with a centralized place to put metadata associated with a
web application. This includes, but is not limited to, the web
application's name, links to icons, as well as the preferred URL to open
when the user launches the web application. The manifest also allows
developers to declare a default orientation for their web application,
as well as how the application is to be displayed by the user agent
(e.g. in fullscreen)."
Intent to implement:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/qz2pd3MFPKg/dzUt2uZdnooJ
Is this feature supported on all five Blink platforms:
Yes and No. First, it's not really implemented in Blink but in Chromium.
Then, it's implemented for all platforms but only used on Android for
the "Add to homescreen" feature at the moment. Otherwise, all the code
about parsing the fetching the manifest and parsing the manifest (ie.
the parts covered by the specification) is implemented for all
platforms.
Demo link:
This is not adding any new API but only new data to be used by current
API and features. Chrome Android will use the Web Manifest for the "Add
to homescreen" feature at some point but unfortunately, there is no
public builds of this yet.
Compatibility Risk:
Microsoft expressed interest in the specification. Mozilla is has a
variation of the Web Manifest in Firefox OS (à la Chrome Apps Manifest).
The attributes that are being supported for now are non controversial
and simple enough to pose no compatibility risk (see specification).
OWP launch tracking bug:
http://crbug.com/366145
Link to entry on the feature dashboard:
http://www.chromestatus.com/features/6488656873259008
-- Mounir