Hot answers tagged confirmation
15
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 ...
13
This may be a case of the more you make users work, the less they try. I believe when confronted with a task, like trying to understand some content on a page, users do a quick estimate on whether the effort will be worth it or not.
Too often we present users with extensive content and clicking just to tell them something that they already know or don’t ...
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, ...
4
If you don't provide the user the possibility to turn off a single confirmation, it looks to me like a bad idea as it will probably be used to turn off a single useless or annoying confirmation without being able to evaluate the whole impact of this action.
A better design may be to add a "Don't display this confirmation again" checkbox to each confirmation ...
2
I want to challenge your descision to revoke their right to any kind of technical support for a service in exchange for being allowed access to beta or in-development features of said service.
How are you going to evaluated those features if you do not have user feedback?
Secondly, why don't you give them access to technical support? Is it for a principle ...
Only top voted, non community-wiki answers of a minimum length are eligible
