Apps

Your phone notifications should tell you what needs a response

· Geeknewz Author

A white smartphone with its screen dark on a wooden desk beside a notebook, pen and closed laptop.
Photo: www.Pixel.la Free Stock Photos / Wikimedia Commons, CC0 1.0. Resized 2014 file photograph; no notification interface is shown.

A delivery driver waiting outside deserves a different kind of interruption from a shop announcing a sale. Both messages might be relevant to you. Only one becomes less useful if you see it after lunch.

That's the distinction I'd put at the centre of phone notification settings: what, if anything, do you need to do before this message can wait? An app's name is a poor substitute for that question. You might want its urgent updates while having no interest in its running commentary.

This is an argument for being more precise about interruptions, rather than trying to make your phone completely silent. The goal is to trust the alerts you leave on enough that you don't feel obliged to inspect everything else just in case.

Decide what waiting would change

Start with a small sample of recent alerts and ask what would have happened if you'd read each one an hour later. Don't judge whether the message was interesting. Judge whether the delay would have changed a decision, inconvenienced someone or cost you a useful opportunity to act.

Imagine three messages from the same delivery app: your order has been accepted, your driver needs help finding the door, and a discount is available next week. The first is reassurance, the second needs a response, and the third is something you can consider when you next want to order. Treating all three as equally interruptive gives the app a simpler rule, but it gives you a worse one.

You can use that distinction without building an elaborate personal system. Keep a short list of things you genuinely want to hear about immediately. Set another group aside for your next deliberate check. Silence the messages you would rather discover inside the app, if you discover them at all.

Those groups should reflect your circumstances. Someone coordinating a family pickup may need a conversation to stay audible. Someone waiting for an appointment slot may reasonably treat a booking alert as urgent. Neither choice needs to become a permanent rule for every message from that person or service.

Separate reassurance from a request

An update can be useful without demanding your attention at the exact moment it arrives. That's particularly important when deciding what you expect from an app, rather than simply deciding which switches to turn off.

Consider a hypothetical subscription service. A reminder that a renewal is approaching could give you time to make a decision. A receipt after a renewal helps you keep records. A recommendation for something else to buy serves a different purpose again. I'd want those choices presented separately, with examples that explain what each setting allows.

The same standard should apply to the message itself. A helpful alert ought to say what happened, whether you need to act and, when relevant, when that action stops being useful. A vague invitation to open the app makes you do the work of finding out whether there was a reason to interrupt you.

That doesn't mean every notification needs a deadline or a button. A friend's photo can be welcome simply because it's a friend's photo. Enjoyment is a perfectly good reason to keep an alert. The important part is that you've chosen that interruption, rather than kept it because the setting was too broad to make a better choice.

There is a trade-off here. Sorting every possible message type would become a chore of its own. A useful settings page should offer a few understandable choices, then let you refine the exceptions that matter. You shouldn't need to design a flowchart before you can comfortably leave your phone on the table.

Change one noisy app first

For your own phone, begin with one app whose alerts you regularly dismiss. Inspect the controls it actually offers; don't assume every service can separate the categories you'd like. Keep the messages you rely on and quiet the optional ones where those controls allow it.

Then give the change a few ordinary days. Notice whether you missed anything you wanted promptly, or whether you're opening the app more often to compensate. If silence makes you repeatedly check for an important update, adjust the rule. You've learned something useful about the job that alert was doing.

Avoid making this an exercise in achieving the lowest possible notification count. A phone that reliably tells you when someone needs you can be more comfortable to live with than one you've silenced indiscriminately. Start with the interruptions you would choose, keep a dependable way for important people to reach you, and let the rest wait for a time you choose to look.