[dangrover]

It doesn't make sense because the barrier to "apphood" in whatever Chrome defines to be an app is scarcely more than making a manifest. The distinction between a chrome app and a webpage is very minimal. What user problem is being solved by this? Why do I need a screenshot of the "app" (i.e. webpage) I am already using?

[dahwolf]

"The distinction between a chrome app and a webpage is very minimal"

It can be minimal, it can be significant difference, all depends on the PWA implementation.

Installed app has a shortcut/desktop icon, which is good for return engagement. A flash screen ratehr than the blunt loading of a web page. The UI can be instantly there as well as some content using offline tactics. A PWA isn't compromised by all kinds of browser real estate.

A proper PWA can definitely be better or approach a proper desktop app, but it's true that few implement them in that rich way.

[pjmlp]

Non technical users.

Secondly, not having Electron all over the place.

[cxr]

You're answering a question no one asked. Please re-read the comment you are responding to.

[LuciusChen]

Every person's computer has many Electron applications, and each Electron application is a Chrome browser.

[vbezhenar]

One of the biggest problems is that users often neglect to use bookmarks. Consequently, as soon as they close your web app, it disappears. By using the "Install" feature, a bookmark is kept in a visible location, significantly improving the chances that users will launch your app again.

This is one of the primary reasons why many developers still prefer to publish in App Stores, despite the various obstacles and risks involved.

Mobile Safari also treats websites differently if users add them to their home screen. It doesn't aggressively remove local storage in these cases. However, I am not certain about Chrome's behavior in this regard.

[cxr]

You have misunderstood the question. Chrome already allows you to "install" these things today. This post is about a change to Chrome's installation UI. Chrome's installation UI will support the "screenshots" property in the installation manifest now.

When the person you are responding to writes, "What user problem is being solved by this?" they are not being asked to have the value proposition of "installable" Web apps explained to them. They are asking about exactly what they say they are: "Why do I need a screenshot of the "app" (i.e. webpage) I am already using?"

[sparsely]

The screenshot of the "app" is useful because the actual webpage you're looking at probably has a newsletter signup modal, misleading cookie banner, and a couple of ads on it.