Your App Does Not Need to Interrupt Every Thought

A person opens an app to complete a task. Before they finish, a promotion appears, a reminder slides across the screen and a badge asks them to explore something new. Each message may make sense to the team that created it. Together, they can make the original task harder to follow.

A useful design question is: what does the user need to know at this moment? That shifts attention from everything a product could announce to the information that helps someone act.

Give quiet use a visible place

W3C’s supplemental cognitive accessibility guidance recommends making interruptions controllable, with exceptions such as emergencies. It describes options including choosing notification types or pausing distracting content. This is supplemental guidance rather than a claim that one setting establishes WCAG conformance. Read W3C’s Limit Interruptions pattern.

For a creator tool, a practical application could be a visible focus setting that holds promotional messages until the user has finished editing. The product can still show feedback that their work has saved. Quiet use should not leave someone uncertain about whether an important action succeeded.

Give each message a reason to arrive

Review the messages your product sends. Which require immediate action? Which can wait in an activity list? Which repeat information already visible on the page? Remove duplication before adding another preference screen.

Consider a fictional writing app. A warning that unsaved work may be lost has a different purpose from a suggestion to try a new template. Showing both with the same visual urgency makes their relative importance harder to judge.

Listen to different experiences

Some people welcome reminders; others prefer to check updates themselves. Avoid treating one preference as the universal setting for all users. Make controls understandable, easy to find and reversible.

A small review can observe whether people finish the task, miss essential information or struggle to find notification settings. Ask about their experience as well as measuring clicks. An interface can attract interaction because it is useful or because people are trying to dismiss it.

For product teams, the opportunity is to make attention a design consideration from the beginning. A quiet screen can still be informative. Let the user decide when ordinary updates deserve a place in their day.