- From: frlinw <notifications@github.com>
- Date: Thu, 25 Jul 2019 18:18:15 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/705/515271735@github.com>
@mgiuca For the user experience, both have value, why was it implemented in Chromium/Firefox UI if not ? You are probably right for the mobile plateform but it's not obvious for desktop. During normal in-browser navigation, if you are used to go to a webapp (already installed) the only thing telling you it's installed is this icon in the address bar. But it's a new feature and most of the time, people don't look at the address bar zone except if they are searching for a specific known feature. So what is the discovering strategy? What if the desktop shortcut is removed? If the user visit the webapp (in browser) and can see in a corner `hey, you already installed the app, use it! [open in app button]`, a click will open the "open with" tooltip (so he'll notice the new icon and discover the feature) and chose to open in app or cancel. > I don't think we want sites to be able to constantly ask the user to switch into app mode Visually, it could just replace the install button, same requirement (user gesture), same [design patterns](https://developers.google.com/web/updates/2019/06/pwa-install-patterns). > if the user rejects switching into app mode once, does that mean they don't want to be asked again It's not a permission but just a shortcut to open the "open with" tooltip. Webauthor don't even need to know if the user closed it. It's the result of a user gesture, if they don't want to be asked again, they don't click. -- 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/705#issuecomment-515271735
Received on Friday, 26 July 2019 01:18:38 UTC