A slightly more complex product is indispensable for the prompt function. This kind of global module requires both an overall solution and specific application rules. Taking the mobile app as an example, there are many types of prompts (successful operation, operation failure, favorite, second confirmation...); there are also many display forms.
I have been thinking about this aspect recently, and I have compiled a set of methods and suggestions for prompt design based on external network data. For the convenience of explanation, the following will take the mobile terminal as an example, but the core method concept is applicable to various terminal platforms.
The following will analyze prompt design from three perspectives - importance, location and content composition.
1. Importance
There are so many types of prompts that it is almost impossible to enumerate completely, and many bug prompts cannot be expected at design time. So a more practical approach is to divide the prompts by their importance. But on what basis? The usability question rating rules I refer to here use "the likely impact on the user if there is no prompt" to judge the importance of the prompt.
If you want to understand the b2b data rating rules for usability problems, you can read this theoretical article I wrote earlier:
1.1 Severe reminder
Changes that are irreversible, involve money, or are not recommended, such as: permanent deletion, purchase, unfollowing…
design direction:
Make sure the user can see the prompt, even if it interrupts the current task
Requires user action or selection to continue
1.2 Moderate prompt
Change information that users may need to know and are interested in, such as: friend messages, network errors, account upgrades…
design direction:
Make sure the prompt is visible to the user without interrupting the current task as much as possible
Does not disappear automatically, but the user can choose to ignore
1.3 Mild tips
Changes that users can expect, such as: successful sending, adding favorites, turning on data saving mode…
design direction:
Avoid any interruptions to the current task and allow interested users to discover hints
Disappears automatically without any action