Re: [manifest] Native API Permissions (#319)

Yes that matches my interpretation.

A web app is a collection of web pages dedicated to a particular task. You can discover new web apps through the web browser, and when you find something you want to keep you can "install"/"pin" it to your device to break it out of the browser and use it standalone.

Some people think that a web app installed to your device should be able to get access to features of the device that it otherwise couldn't when you're just "browsing" it.

In order to grant permissions to a web app we also need to agree on the identity of a web app (see #272) so we know what we're granting permissions to. I still think the manifest URL is the best identifier (I know I haven't convinced Marcos of this yet). The manifest describes the URL scope of the app in the scope property, so that you know which resources you're granting permissions to.

A permissions property could describe the maximum permissions an installed app can request, and perhaps even some permissions which are implicitly granted by simply installing the app. (We kind of already do this in a way, the standalone display mode allows an installed web app to hide the URL bar, which it couldn't do in the browser).

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/319#issuecomment-77558936