The Microsoft Edge team (and in extension the #PWA team at Google Chrome) is looking for feedback on developer preferences when it comes to Web Install:

- declaratively using the `<install>` element (https://github.com/WICG/install-element)
- imperatively using the `navigator.install()` API (https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall%2Fexplainer.md)

You can provide your feedback on the GitHub Issue: https://github.com/WICG/install-element/issues/23.

GitHub - WICG/install-element: An `<install>` element might be nice.

An `<install>` element might be nice. Contribute to WICG/install-element development by creating an account on GitHub.

GitHub
@tomayac IMO we need less application-platform-ness on the web, not more. A web browser is first and foremost a hypertext document viewer, not an application runtime.
@grishka I don't agree with this opinion, but acknowledge that you're not alone with it.
@tomayac I thought it was already figured out with web application manifest
@jason The manifest serves for providing metadata about an app that both install methods use.
@tomayac if the user cannot validate the source/intent/function of this “web app” what are they installing and what does install in a web browser mean?
1. Shortcut on homescreen or desktop?
2. installing an extension
3. something else?
@dahukanna See this article for some of the features an installation enables: https://web.dev/case-studies/svgcode.
SVGcode: a PWA to convert raster images to SVG vector graphics  |  web.dev

Convert color or monochrome bitmap images (PNG, JPG, JPEG, WEBP, AVIF, GIF,…) to color or monochrome vector images (SVG).

web.dev
@tomayac thanks and will take a look.
@tomayac hasn’t WebKit and the WG already stated preference for the declarative install-element?