What is the point of thread-id/grouping in push notifications if grouping depends upon user preferences?

Question

Created Mar ’25

Replies 1

Boosts 0

Participants 2

There's plenty of articles out there about programatically grouping push notifications. However I have tried setting the thread-id in the push payload when sending a push, or setting the threadIdentifier for a received push in a notification service extension to be the same for several pushes.

But if within the iPhone Settings / Notifications the user selects to display pushes as List and turns off Notification Grouping, then each notification resulting from the push appears on its own separately.

Is there something other than thread-id/threadidentifier that is used to programmatically group them? If not then whats the point of these as grouping and display is actually under the control of user.

Boost

Answer 1

Engineer OP

Apple

Mar ’25

Whether an app can even send notifications, how they are displayed, when they are displayed or not, are all under user control. The users control what they see and how. That is the point.

Anything an app does to show or configure notifications will work unless the behavior is overridden by the user, who is the one in charge.

The important point is that apps should never be designed expecting that every push notification will be shown as expected. Apps are expected to work properly, albeit perhaps with degraded functionality, if push notifications are not shown as desired, or even turned off, as the user can turn off visibility push notifications at any time, along with restricting their display to certain times, or even send them to the daily summary.

0