Re: [w3c/manifest] Add `navigator.install()` (PR #1175)

benfrancis left a comment (w3c/manifest#1175)

I'm fascinated to see how this pans out given we now seem to have gone full circle from [`navigator.mozApps.install()`](https://hacks.mozilla.org/2013/02/getting-started-with-open-web-apps-why-and-how/) in ~2012, and in the intervening time browser vendors have gone to great lengths (installability criteria, install prompts etc.) to avoid doing this.

Some questions:
- Is the intention still to eventually [require that a manifest contains an `id` member](https://docs.google.com/document/d/19dad0LnqdvEhK-3GmSaffSGHYLeM0kHQ_v4ZRNBFgWM/edit?tab=t.0#heading=h.2ex5jpno4wi8) in order for installation to succeed?
- If `navigator.install()` only works if the document links to a valid web app manifest, does this not further reinforce the idea that [a web app needs a web app manifest in order to be installable](https://github.com/w3c/manifest/issues/1168) (contrary to the [definition recently added to the specification](https://github.com/w3c/manifest/pull/1163))?
- Are we OK with the idea that this will cause the web to be littered with install buttons (which as I understand it is the reason browser vendors have avoided doing this so far)?

I think on balance my advice (in the capacity of an Invited Expert) would be to *not* add this feature to the web platform, but to instead focus on how to improve the user interface that user agents provide to install web apps.

It is already possible for browser vendors to implement an "install app" feature inside user agents, which could be a more prominent and trusted user interface than an install button in each web app (e.g. an ambient indicator in a URL bar to indicate the current document is part of an installable web app, and a prominent "install app" button). Instead this feature currently tends to get buried inside multiple levels of menus or use obscure language like "add to home" rather than "install". Unfortunately I think this poor user experience is a result of misaligned incentives of the current incumbent "user agents" rather than a lack of creativity in user interface design.

If browser vendors continue to bury and obfuscate the install app feature then I can see why this API would be necessary, but I think the resulting user experience (spammy install buttons and prompts everywhere) would be worse for everyone.

---

As an aside, this is another example of something that could be much simpler to implement if a web app was identified by its manifest URL (`navigator.install({manifest URL})`).

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

Message ID: <w3c/manifest/pull/1175/c2962366273@github.com>