- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 11 Jun 2020 00:57:49 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 11 June 2020 07:58:02 UTC
@marcoscaceres commented on this pull request.
> + Marketable web applications
+ </h2>
+ <p>
+ As web applications become available via more services (e.g., digital
+ storefronts, search results) where they are presented alongside native
+ applications, it becomes quite important for them to appear similarly
+ to their native counterparts. A web application can define both its
+ {{WebAppManifest/name}} and {{WebAppManifest/icons}} in the manifest,
+ but those keys do not provide enough information to help users
+ determine whether they might want to install it. Users have become
+ accustomed to being offered more details about the applications they
+ consider installing, and this document defines additional manifest
+ members that can provide that.
+ </p>
+ </section>
+ <section id="processing" data-link-for="WebAppManifestAppInfo">
As this is not running in a browser, there is no need to add processing steps. There will not be any conformance steps.
We can add steps where we feel there might be interop issues.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/900#discussion_r438609034
Received on Thursday, 11 June 2020 07:58:02 UTC