[kanonieer]

> We’re excited to announce the availability of a new PWA feature that closes this gap and helps blur the line between apps and websites even more.

I don't see how they can use "blurred line" as a positive trait here. There are important differences between native apps and web apps, why hide this information from a regular user, especially when this information can be conveyed by 30 pixels.

[drewtato]

Well right now, the alternative isn't "keep it in the browser", it's "ship it in electron".

[int_19h]

We're talking about web apps that are specifically intended to be installed locally and look like native apps. What are those "important differences" in this context?

(and note that you can still use PWA in the browser if you want to, and thus deny it this ability)

[chpmrc]

What difference does the runtime make to the (average) end user? I love that I can create shortcuts of some web apps that have their own window, menu bar etc. (this is already possible in Chrome) and I don't really care they are "web" apps.

[LtWorf]

> What difference does the runtime make to the (average) end user?

"Incredibly slow and draining the battery 3x as fast" vs "regular"

[chpmrc]

That has nothing to do with the runtime, rather with the implementation. Barrier to entry of web development is low so average quality is also low. On the opposite side of the spectrum you have products like Figma, Notion, Google apps etc.

[make3]

because actual regular answers don't understand what any of this means, and this just means that the devs have more control over what experience they give them