Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051)

jyasskin left a comment (w3ctag/design-reviews#1051)

Hi! First, thank you for adjusting the proposal in response to some of our previous feedback, in particular [removing `install_sources`](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer.md#install_sources-manifest-field) and [postponing `navigator.getInstalledApps()`](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer.md#future-work). I don't see adjustments or explanations in response to some of the other [comments](https://github.com/w3ctag/design-reviews/issues/946#issuecomment-2345373071):

* The ["Declarative install" alternative](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer.md#declarative-install), which mentions `<a target>` doesn't mention our suggestion to consider `rel`.
* The TAG felt like it was probably better for users if they can interact with the to-be-installed site before being asked if they want to install it. The [Declarative Install alternative](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer.md#declarative-install) says that "Takes the user out of the current context." is a downside, but the TAG currently disagrees that that's a downside and would need to be convinced. What data have you collected that shows that it's bad for users to have to visit a website before installing it? A "peek" UI like https://resources.arc.net/hc/en-us/articles/19335302900887-Peek-Preview-Sites-From-Pinned-Tabs might also offer a way to get the best of both options.

We don't expect to review this again in detail before our comments from last time are more fully addressed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1051#issuecomment-2685948570
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1051/2685948570@github.com>