Size: 1288
Comment:
|
Size: 1167
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from ExitGuard 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. |
== Problem == Exiting a screen, process or application could cause a catastrophic (unrecoverable) loss of data, or a break in the session. |
Line 5: | Line 4: |
SOLUTION: | == Solution == |
Line 8: | Line 8: |
VARIATION: | == Variations == |
Line 12: | Line 13: |
== Problem == == Solution == == Variations == |
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.
Variations
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.
Interaction Details
Presentation Details
Antipatterns