W3C home > Mailing lists > Public > public-web-mobile@w3.org > November 2013

Re: New manifest spec - ready for FPWD?

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 26 Nov 2013 14:00:32 -0800
To: Marcos Caceres <w3c@marcosc.com>, "public-webapps@w3.org" <public-webapps@w3.org>
CC: "kenneth.christiansen@gmail.com" <kenneth.christiansen@gmail.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Web and Mobile IG <public-web-mobile@w3.org>
Message-ID: <CEBA55DC.342C1%stearns@adobe.com>
On 11/26/13, 1:02 PM, "Marcos Caceres" <w3c@marcosc.com> wrote:

>Over the last few weeks, a few of us folks in the Web Mob IG have been
>investigating the use cases and requirements for bookmarking web apps to
>home screen. The output of that research  is this living document:
>That (ongoing) research is helping to inform the manifest spec. A bunch
>of us have been working together on IRC, twitter, etc. on a new version
>of the manifest spec:
>The Editors would appreciate if people take a look and see if you agree
>with the feature set.

Are there any connections between the new Manifest spec and the
configuration document specified [1] in Packaged Web Apps? Have all of the
attributes that go into a configuration been considered as possible
Manifest members?

Going by the use cases document, there are at least two characteristics
(offline, no navigation bar) that define a standalone app. Are there any
more characteristics that a standalone app should have? Should these be
noted in the spec? Could there be any benefit to enumerating these
characteristics in the manifest? Iım wondering whether it would be useful
to say that the web app provides a native app UI but still requires the
device to be online.



[1] http://www.w3.org/TR/2012/REC-widgets-20121127/#configuration-document
Received on Tuesday, 26 November 2013 22:01:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:59:28 UTC