 Atom Homescreen has a concept almost as old as the original iPhone. In fact, Atom Homescreen was introduced in February 2008 with iPhone OS 1.1.3. Today, more than 10 years later, Atom Homescreen has come a long way, and what started as a mere bookmark has now turned into a PWA superpower. My name is Tom and as you've guessed, today I want to talk about Atom Homescreen. Let's get going! Chrome first introduced Atom Homescreen banners in Chrome 42. We're talking May 2015. We've heard from developers like Alibaba that users re-engage four times more often with their app at Atom Homescreen. So in the early days, it seemed like getting users to install a PWA was an immediate recipe for success. In consequence, we tuned the heuristics for Atom Homescreen to prompt users sooner, which yielded to 48% more installs. In hindsight, this alone wasn't directly correlated with other app success metrics that you as an app developer would care about, such as conversions. We introduced an improved variant of the feature in Chrome Beta 57 with better integration into Android, so apps were no longer just bookmarks. Other new features included the ability to change the app icon and app name by changing the values in the web app manifest, and also to register a scope of URLs where the app would be launched directly. But we've heard one thing loud and clear. Developers want more control as to when their apps show the banner. For example, if you're an airline and you have a PWA for storing boarding passes, of course, it only makes sense to ask people to install it after they've actually bought a ticket. If you're a new site and your users are all logged in, it might make sense to show the prompt immediately. And in some cases, even if you have a fully qualifying PWA, you might not even want to show the prompt at all. But most probably, you would want to define your own criteria in your app to determine who is a loyal enough user to show the banner to. Let's see how we can do that in our good old friend AffiliCats that we've introduced in our last two episodes. It simulates a comparison site where you can get great deals for cats. AffiliCats makes money when someone clicks through to one of the deals. The app meets the PWA installability quality bar in Lighthouse, but we're going to hold back the prompt until someone has actually viewed at least two deals. Should the user come back to the app, which hopefully they do, we can then show them a customized button that will trigger the browser's prompt. We're in full control. Add to the home screen as a superpower that, if used wisely, can indeed have a massive impact on how users use your PWA. And if they perceive it as a real app worth a precious space on their home screen. Thanks for watching and see you next time. If you like this series and want to see more, let us know in the comments.