New answers tagged user
2
Confirm if a) the user might want to undo, but b) won't be able to.
Design to avoid a) and b).
14
User confirmation is almost always a bad solution. It breaks the user's flow and there's a real risk of habitually clicking yes on the confirmation. It basically makes 99% of the actions require more attention to catch the 1% that go wrong. And it works poorly. This article explains it better than I can:
http://alistapart.com/article/neveruseawarning
Of ...
0
Confirmation From user is required in some conditions which are given below :-
When the user activity looses some data or changes in some structure of information heavily.
When user enters or leaves a secured environment.
When accessing hardware or interacting with other programs or structure.
When user possessing any payment method successful or failure.
...
5
Confirmation is warranted when
User initiated action will have significant consequence which cannot be undone
The user initiated action itself may not be risky, but there is a severe side effect of the action that user needs to be aware of
Please refer to http://www.uxdesignedge.com/2010/06/are-you-sure-how-to-write-effective-confirmations/
Note:
But, ...
Top 50 recent answers are included
