Re: [w3c/manifest] The new definition of "installable web application" is inconsistent with the normative text of the specification (Issue #1168)

benfrancis left a comment (w3c/manifest#1168)

For comparison with where we started, in the original [Use Cases and Requirements](https://w3c-webmob.github.io/installable-webapps) document for this specification (now a decade old):

> 11. Requirements
>
> A standardized solution:
> - MUST provide a mechanism that allows a developer to indicate that the application is able to function as standalone. If no such indication is given by the developer, then the application MUST launch in the Web browser as normal. That is, the solution MUST NOT conflate bookmarking with allowing a web application to be launched as standalone.

It's actually remarkable how closely today's specfication matches that set of requirements, and how the "standardize an API for adding web applications to the homescreen" is still being debated today.

But it sounds as though browser vendors have a different set of requirements today that are maybe worth documenting, whether they are implemented by this specification or another one.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1168#issuecomment-6218042999
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1168/6218042999@github.com>