Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)

dmurph left a comment (w3c/manifest#1092)

@helo-sky said:
> I assume the value of `window.standalone` changes depending on the window context, right? For example, if the app is installed and opened as a standalone app, `window.standalone` would be `true`. However, if I open a new tab in the browser for the same website, `window.standalone` would be `false`, even if the PWA is installed and running in the background. Is that correct?

This highlights a problem with the name `standalone`.... and `installed`....

On Chromium, as @DanielHerr points out, you can configure the installed pwa to open in a browser tab or a standalone experience. This windowing situation is a separate concept than whether the PWA has had it's capabilities integrated with the operating system. From most of the requests for this feature, the problem was based around the fact that the `fullscreen` display mode made it confusing to detect if the... wrapping chrome?... was a pwa standalone experience or a browser tab. This is attempting to solve that.

If we also want to detect if the pwa is installed with os integration, that is possible today on Android (and hopefully soon on desktop) on chromium with the [getInstalledRelatedApps()](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/getInstalledRelatedApps) API, where the page can request if it's own app id is installed.

What do people think about all of this?

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

Message ID: <w3c/manifest/issues/1092/2878178357@github.com>