|
Size: 629
Comment:
|
Size: 1209
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ...they are very similar in interaction, BUT are very different cases.Exit an app or process, vs. cancel an action (e.g. abandon a text field that might have taken a long time to enter stuff on). Exit can usually live with interstitials, but cancel often must be more inline. Or maybe even other methods of protection such as saving data, allowing exit, but then telling user they can go back to enter it again... Refer to clear fields in text entry as well... | ## page was renamed from CancelGuard PROBLEM: User entered data or subsidiary processes would be time consuming, difficult or frustrating to reproduce if lost due to accidental user-selected destruction. SOLUTION: Methods must be provided to protect input and 1) Design and technical systems to avoid this. Save user data for future or recovered entry. Etc. What else??? Or included in the below items already??? 2) Implicit protection: Design interactive methods to avoid exit or deletion. E.g. if deleting a field, and the convention in the OS would make an additional delete key press exit the field, and give focus to the next field, do not do this on key repeat, to avoid accidentally deleting multiple fields. Add a pause, or a hard stop, so the user must release and re-press the delete key. 3) Explicit protection: When a single function is provided to clear user entry, provide a method within the screen (not a popup, but something right next to the field or function) to allow recovery of the user-entered data. |
PROBLEM: User entered data or subsidiary processes would be time consuming, difficult or frustrating to reproduce if lost due to accidental user-selected destruction.
SOLUTION: Methods must be provided to protect input and
1) Design and technical systems to avoid this. Save user data for future or recovered entry. Etc. What else??? Or included in the below items already???
2) Implicit protection: Design interactive methods to avoid exit or deletion. E.g. if deleting a field, and the convention in the OS would make an additional delete key press exit the field, and give focus to the next field, do not do this on key repeat, to avoid accidentally deleting multiple fields. Add a pause, or a hard stop, so the user must release and re-press the delete key.
3) Explicit protection: When a single function is provided to clear user entry, provide a method within the screen (not a popup, but something right next to the field or function) to allow recovery of the user-entered data.
Problem
Solution
Variations
Interaction Details
Presentation Details
Antipatterns