Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like Apple's growing approach of distinguishing "Time Sensitive" notifications and "Live Activity" notifications from all the other types of notifications from an app.

An Uber Eats delivery is a "Live Activity" with a tracker that is sticky on the lock screen (and Apple Watch "activity area"). That makes a lot of sense. "Deals" and other random garbage Uber Eats wants to send to me aren't "Live Activity" so can be filed to later/slower delivery.

A buzzer notification from my condo buildings front door is a "Time Sensitive" notification that gets priority. But that same app's "weekly neighbor updates" isn't and can be filtered differently. Those things are great.

I can send most notifications to "Notification Summaries" which give me digests of all the notifications in roughly ~4hr chunks. There are very few things that I need faster than that (esp. when apps properly support "Time Sensitive" and "Live Activities").

Of course, with great power comes great responsibility. I've caught LinkedIn abusing "Time Sensitive" notifications (because of course it would, LinkedIn loves notification spam too much not to) and entirely revoked its privilege to send them.



That sounds pretty great, especially if it's handled from the developers side and we don't have to customize it.

I know I can customize notifications for my apps but when I go to look at it an app has like 50 different types and I just don't care enough to deal with that so I just mute the whole app instead.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: