The thing that is missing from notifications is receiver context. The time that the notification is pushed doesn't mean that is the time that I want to receive

The thing that is missing from notifications is receiver context. The time that the notification is pushed doesn't mean that is the time that I want to receive them. When I'm driving I don't need a notification to tell me the latest sports score, in fact it would be a distraction. But I do want the notification telling me that the meeting I'm driving to has been rescheduled or that there is an accident up ahead and if I leave at the next junction I won't be stuck in traffic for an extra 30 minutes. Bill payments are set-up on a Sunday evening so no point reminding me on a Tuesday morning, as I'll just forget by Sunday. Facebook you can prod me at lunch-time or in the evening, providing I'm at home and not engrossed in a film. Breaking News maybe I want to know, but if it's really just an update and you don't know anything more than you knew 2 hours ago then don't waste my time. The challenge is that the notification publisher doesn't know my schedule or context so will never know whether it's a good time for me to receive the notification. The device I'm using might have some explicit or implicit insight into my schedule/context but it doesn't have any detail on what the notification is about and whether I would want to receive it now. Putting the fine grained control for type of notification and time of day/day of week in the hands of the user might help, but realistically it's only a subset of users who will invest the energy in configuring this. A learning notification filter is the only way I can see that it would be simple enough for most users to benefit.