|
Size: 1252
Comment:
|
Size: 2494
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| PROBLEM: Exiting an app, or entire process. And the exiting could cause a catastrophic (unrecoverable) loss of data, or break in the session. Need to prevent this from happening. SOLUTION: Present a modal dialogue which delays the user from exiting immediately (the app or function is kept open in the background), informs them of the consequences of exiting (loss of data) and requires them to make choices, at least confirm exit or return to session. VARIATION: Timer inside exitguard, so you do need just one action to exit. Two actions will exit immediately, but one will exit after a few seconds. Timing depends on users and expected environment. Be sure to notify (sound and/or vibration) so users look at the screen! OR: opposite. For very high criticality apps, have a limited time to hit the pop up and accept exiting. Else, returns to the running app. A version of this is the press-and-hold power (or a button) to turn off. This is not discoverable so a dialogue must appear immediately (and stay up after release of the button) to tell the user HOW to exit. |
|
| Line 13: | Line 2: |
| Exiting a screen, process or application could cause a catastrophic (unrecoverable) loss of data, or a break in the session. | |
| Line 16: | Line 6: |
| Present a modal dialogue which delays the user from exiting immediately (the app or function is kept open in the background), informs them of the consequences of exiting (loss of data) and requires them to make choices, at least confirm exit or return to session. Build systems to prevent data loss even if exiting occurs. For example, auto-save all user entry, save draft messages, etc. In many cases, even critical entry systems may forgo an '''Exit Guard''' as long as recovery is simple and the process may be easily re-initiated. For high security or time-sensitive entry, such as banking, it may be implausible to auto-save information with sufficient security, or a break in the session may cause too much delay. In these cases, an explicit '''Exit Guard''' is useful. |
|
| Line 19: | Line 14: |
| The most typical variant is a simple modal dialogue, informing the user of the risk of exiting, and presenting a choice to exit or return to the previous state. Sometimes, additional options may also be presented. These are usually special exit conditions, such as choosing to exit with or without saving. A variant uses the '''Wait Indicator''' and a delay timer to provide one-click exiting, as long as the user is willing to wait a short time. For immediate exit, an "Exit now" button can be selected. A sub-variant of the timer, used for high criticality applications, reverses the process. The user must select to exit in a short time (or continue pressing the exit button for a designated time period) or the process will not terminate and will return to the last state. |
|
| Line 25: | Line 27: |
| buzz when presented or they might not notice... When the delay timer is configured so the user must continue an action, a dialogue must appear as soon as the exit function is selected, to inform the user how to exit. If used in the condition where a function must be continuously pressed for a certain time to exit, state how long, and provide a countdown so the user knows how much longer they have. If the button is released before the time required to exit, the dialogue should remain on the screen for several seconds so the first time user, more familiar with short presses and taps, has a chance to learn the process. |
Problem
Exiting a screen, process or application could cause a catastrophic (unrecoverable) loss of data, or a break in the session.
Solution
Present a modal dialogue which delays the user from exiting immediately (the app or function is kept open in the background), informs them of the consequences of exiting (loss of data) and requires them to make choices, at least confirm exit or return to session.
Build systems to prevent data loss even if exiting occurs. For example, auto-save all user entry, save draft messages, etc. In many cases, even critical entry systems may forgo an Exit Guard as long as recovery is simple and the process may be easily re-initiated.
For high security or time-sensitive entry, such as banking, it may be implausible to auto-save information with sufficient security, or a break in the session may cause too much delay. In these cases, an explicit Exit Guard is useful.
Variations
The most typical variant is a simple modal dialogue, informing the user of the risk of exiting, and presenting a choice to exit or return to the previous state.
Sometimes, additional options may also be presented. These are usually special exit conditions, such as choosing to exit with or without saving.
A variant uses the Wait Indicator and a delay timer to provide one-click exiting, as long as the user is willing to wait a short time. For immediate exit, an "Exit now" button can be selected.
A sub-variant of the timer, used for high criticality applications, reverses the process. The user must select to exit in a short time (or continue pressing the exit button for a designated time period) or the process will not terminate and will return to the last state.
Interaction Details
Presentation Details
buzz when presented or they might not notice...
When the delay timer is configured so the user must continue an action, a dialogue must appear as soon as the exit function is selected, to inform the user how to exit. If used in the condition where a function must be continuously pressed for a certain time to exit, state how long, and provide a countdown so the user knows how much longer they have. If the button is released before the time required to exit, the dialogue should remain on the screen for several seconds so the first time user, more familiar with short presses and taps, has a chance to learn the process.
Antipatterns