3 ms·
One thing is that some times some things have to be made harder for end users good or for business rules protection. It is sometimes hard to explain but as an
by ozim 3y ago
One thing is that some times some things have to be made harder for end users good or for business rules protection.
It is sometimes hard to explain but as an example - delete confirmation - it gets in the way of user because user wants to delete stuff and be done with it. Preventing accidental deletes is more important than any specific user convenience.
Keep in mind this is most generic example I came up with on the spot. There are more complex scenarios that are complex for the same reasons. But I find people trying to remove such fences even if they don’t know why they’re there. Claiming simplicity and user convenience as golden rule.
- Kranar 3y agoI really detest that principle. For the design of my software I make almost every action reversible and avoid at all costs confirmation dialogs or anything that makes it seem like the user could be at fault for something if they choose incorrectly. I also work on financial trading software so I do need to think a great deal about user error and the best principle I have found is to never create a situation where a confirmation is needed. Among new users it creates anxiety and indecisiveness, and among experienced users they just ignore it and it's noise to them. All confirmation dialogs do is make the developer/designer punt responsibility off to the user for what is generally a bad design decision.