search

w3c-webmob / installable-webapps

Use cases and requirements for installable web apps
43 stars 13 forks source link

Document that standalone is a user decision. #42

Open marcoscaceres opened 10 years ago

marcoscaceres commented 10 years ago

Need to change the following:

"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. "

... to make it clear that it's actually a user's decision, but the manifest format needs to give the developer control over some start-up options for standalone.

nrooney commented 10 years ago

How about:

"MUST provide a mechanism that allows a developer to indicate that the application is able to function as standalone. In the instance when no such indication is given by the developer and the user has not made a previous configuration, 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."

Urgh maybe not..., I'll keep thinking...

marcoscaceres commented 10 years ago

It's really about allowing the developer to say what should happen when the application starts up as standalone (rather than indicating that it can run as standalone, as that is a user decision and not a dev decision!): that is, what orientation and view mode the application should be in when it boots up... as well as what the start URL is and so on.