Add to homescreen changes in Chrome 68 – Pete LePage

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan

<p>Pete LePage writes about important changes to Add to Homescreen in Chrome</p> <blockquote> <h2 id="add-to-home-screen-changes">Add to Home Screen changes</h2> <p>If your site meets the add to home screen criteria, Chrome will no longer show the add to home screen banner. Instead, you’re in control over when and how to prompt the user.</p> <p>To prompt the user, listen for the <code>beforeinstallprompt</code> event, then, save the event and add a button or other UI element to your app to indicate it can be installed.</p> </blockquote> <p><a href="https://developers.google.com/web/updates/2018/07/nic68">Read full post</a>.</p> <p>I had mixed feelings about this originally because so many people don't handle the <code>beforeinstallprompt</code> event it meant that all of a sudden the number of installs of Web APK's would drop quite significantly, but I think it's actually the right thing to do.</p> <p>The goal is to reduce the number of annoying prompts happening on the web, and the last thing that we need in the industry is for a relatively large prompt to appear when we think the user might want to install a PWA, instead you now need to think about where and when <strong>you</strong> want to prompt for an install and you have to do it in response to a user-gesture.</p> <p>The neat thing is that we (Chrome) are introducing more ambient ways of letting the user know that an experience is able to be installed, right now it's the small bottom bar that appears on the first load, and hopefully in the future we can explore more subtle ways of letting the user know they can take action.</p>

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan