Here is proof that it is an intentionally-bad feature:
Web pages can tell if you enabled notifications.
The last time I checked, Slack used this to break unrelated functionality until you gave it browser notification permission, and re-broke itself if you disabled permissions after enabling them. Otherwise, there is no reason to enable it or install the app. (You can deny notifications per app, at least on apple platforms).
Same with iOS (and I presume Android)! So many apps will add extra nags inside the app until you enable notifications. But then as long as you do, they'll send you spam notifications on a frequent basis.
Microsoft 365 [whatever/copilot] apps on Android. If you enable notifications in Outlook you course get notifications when it updates to new version.
Or the Office app shows a notification that it can open every PDF you download.
One of the most impactful things I've done with enterprise security, and I mean moreso than buying any expensive product, was deployed a browser policy that disabled browser notifications (and deployed ublock). Service desk calls from people claiming to have been hacked because their browsers kept popping up scare ware ads dropped to nothing overnight, with a notable drop in complaints and absolutely zero complaints logged about people who wanted notifications on something. It's obscene, the desktop notification feature has generated more work for security people than active directory and it's lack of mfa support.
They’re plenty useful when used by a service you engage with. I run Slack as a tab in my browser rather than as a standalone app and browser notifications make that usable.
Can't imagine myself doing that at work. People still ask me why it always takes me hours before responding to their messages, many of which are time-sensitive.
They lost me right there. They are not a useful feature and should not exist.