In D15212#341959, @emack wrote:

Refresh page in PWA, see udpate modal. On update, the form label has changed.

Manually refreshing PWA tested all ok, pulling in the latest update. However thinking from an UX pov, most users wouldn't think to manually refresh their PWA if they were unaware that there was an update in the first place. There was a period of time where quite a few users messaged in the tg for help with screenshots without the hamburger icon, which was easy to identify.
Is this where a proper push notification mechanism comes in?

We already show users a modal that updates - the issue is that the app is sometimes not realizing an update is available and not showing the modal.

This could be further optimized. For now, though, I want to make sure the problem of PWA users being stuck on an old version is solved. At the moment, the only consistent solutions are

• wait for variable amount of time until PWA does finally update itself (seems to depend on browser/device, user cache settings)
• delete cookies, which works every time but also deletes wallets

These options are unacceptable.

Is this where a proper push notification mechanism comes in?

Not really -- check out the article in the diff description. PWAs have some of their own intricacies, but it is distinct from browser push notifications. These would allow for features like incoming tx notifications when the user is not actively browsing the app.