- From: frlinw <notifications@github.com>
- Date: Thu, 12 Dec 2019 12:39:23 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 12 December 2019 20:39:25 UTC
> We don't want to give away that control to web apps / sites. Specs cannot give recommandation about the UI, so each browser can have it's how way to implement an install/a2hs UI and the burden of education will be on the developer. And even if browsers share a similar experience, it won't be natural for the user to install an app (especially during the education period), so as a developer you'll have to promote it with UA sniff and this kind of intrusives things https://user-images.githubusercontent.com/870154/39285397-80ea3b34-495b-11e8-8e1e-b84861125bbd.png https://github.com/mozilla/standards-positions/issues/84#issuecomment-384507840 With `beforeinstallprompt`, developer can provide a better & consistent UX to install/a2hs (and it's just a shortcut which triggers the browser install process, not the install process itself). It's maybe not perfect, it could be reworked but remove it won't help (me - as a dev - and my users). -- 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/835#issuecomment-565177053
Received on Thursday, 12 December 2019 20:39:25 UTC