[nonameiguess]

Somewhat real-time chat with a human I'm talking to on purpose is the only legitimate use case I can think of and the only thing I enable any sort of push notification from at all, but even then, only from native apps. If the only reason this needs to be in a browser is saving time for the developer, that isn't a good enough reason for me as a user as long as other options exist that use native apps.

Even to use this theoretically, though, I'd want the strict ability to control who can even send me a direct message. As it stands, the only thing I currently allow push notifications for are SMS and Signal, but the SMS texts are still overwhelming election spam from people who aren't even trying to spam me but have the wrong number for my mother or grandmother and bulk property buyers who claim they want to buy one of my houses. So I hope you plan to enable user-controllable proactive origin filtering (not after the fact user-by-user blocking).

[nevi-me]

>If the only reason this needs to be in a browser is saving time for the developer, that isn't a good enough reason for me as a user as long as other options exist that use native apps.

Consider food delivery services (from the reastaurants). We actively order food directly from the reastaurant where possible, because Uber Eats charge more for the food and still charge "service" fees + delivery.

I've just checked, and I have 7 (including Uber Eats) food and grocery delivery apps.

It would be my preference if I dealt with a PWA instead of having to install many apps with varying quality. A notification of the status of my order is useful, and with the grocery apps, sometimes an item that I've ordered is out of stock, and I have a small window to take some action (if I hadn't chosen one when ordering).