Google today announced a major change to its Chrome Web Store policy that aims to shield users from websites that try to fool them into installing their Chrome extensions. Until now, developers who publish their apps in the Web Store could also initiate app and extension installs from their own websites. Too often, though, developers combined these so-called “inline installs” with deceptive information on their sites to get users to install them. Unsurprisingly, that’s not quite the experience Google had in mind when it enabled this feature back in 2011, so now it’s shutting it down.
Starting today, inline installation will be unavailable to all newly published extensions. Developers who use the standard method for calling for an install from their site will see that their users will get redirected to the Chrome Web Store to complete the installation.
Come September 12, 2018, all inline installs of existing extensions will be shut down and users will be redirected to the store, too. Come December and the launch of Chrome 71, the API that currently allows for this way of installing extensions will go away.
“As we’ve attempted to address this problem over the past few years, we’ve learned that the information displayed alongside extensions in the Chrome Web Store plays a critical role in ensuring that users can make informed decisions about whether to install an extension,” James Wagner, the product manager for the extensions platform, writes in today’s update. “When installed through the Chrome Web Store, extensions are significantly less likely to be uninstalled or cause user complaints, compared to extensions installed through inline installation.”
As Wagner notes, inline installations have been an issue for a long time. Back in 2015, for example, sites that tried to deceive users into installing extensions by getting them to click on fake ads or error messages were the main issue.
