[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?"