Re: [w3c/manifest] Ability to detect if the current document is part of an "installed" web app (#454)

> I imagine one can check with the Cache API - to see which version is download, and other cache information. However, the end-user may have modified aspects of the manifest (through the browser's provided install UI).

This raises another question. How does the developer know what the properties of the current manifest are? i.e. How do they know if the user has over-ridden some values or which version of the manifest is being used?

>If a developer needs to encourage installation, then the browser has completely failed: progressive web apps are supposed to solve this exact problem: 

>https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/ 

>It's too early for us (browser vendors) to admit defeat here. We only have two shipping UAs and I think only Chrome is making use of installability signals. 

It sounds like you're saying you want browser to intentionally make it difficult for a developer to detect how their app is being presented to the user? If not, then that suggests there are other ways they could detect this anyway so having a `getCurrentManifest()` wouldn't make the situation worse it would simply make life easier for developers with good intentions.

---
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/issues/454#issuecomment-212954351

Received on Thursday, 21 April 2016 14:46:52 UTC