Tag Info

Hot answers tagged

8

Great question. I've been thinking a lot about "confirmless deletes" because of a behavioral issue with models that is outlined here. In short, most users actually intend to delete an item when they initiate the interaction, so throwing up a traditional confirmation is annoying most of the time. I totally agree with Lauren's answer on the basic ...


5

My suggestion: Delete John Doe? You will lose his financing and payout information. [Cancel] [Delete] Make clear what action will occur. Use verbs in the text.


4

How critical/catastrophic would this operation be? Trivial: no prompt needed; rather, provide a simple undo button. Non critical or easily undone: prompt near the button, as to not annoy users too much and make them lose focus. Critical and can't be undone: centered in the page


4

Severity and recoverability of the action can help guide the style you use. Also the platform you're on. Platform standards also playing a role. Dialog vs. Undo This was discussed in the following Q&A. When dialogs vs. undos make sense: Deletion: Confirm or Undo? Which is the better option and why? Slide to Delete Gestures on mobile devices ...


3

Navigating as a side effect of some other action is not a good idea, I feel. Similar to pushing the user around... Why not show an empty Topic page where some stuff looks like it will look after approval, such as title and creator link (if any), while the content area (where posts will appear after approval) shows a message saying "Topic is waiting for ...


2

Yes, I'd say you are correct. The standards are: let the user do what they want to do, but provide a way to undo let the user do what they want to do, but confirm before doing


2

The answer, not surprisingly, is "it depends on the app". (eg how catastrophic is the loss, is it recoverable, how familiar are users with the app, and other parameters that are specific to your application). But the good news is, you've already laid out the options very thoughtfully in order of progressive levels of disclosure, so you're 90% of the way ...


1

Loss of data is classified with the highest of severity when it comes to design issues. So only go with option 1 if you are 100% sure that the user will know what he is doing. Option 2 will lead to frustration. The last thing you want to tell your users is that an action may have negative consequences. They'll immediately hesitate, and wish that you'd ...


1

Allowing the user to confirm or cancel the deletion more closely to the Delete button provides better context, and a faster interaction. Fitts’s Law is a good reference for this question. Fitts’s Law “predicts that the time required to rapidly move to a target area is a function of the ratio between the distance to the target and the width of the target.” ...


1

Feedback If your entity creation process has "serious" implications for your users, and especially if it may involve them taking actions outside your app (booking a ticket somewhere, buying something and retrieving a tracking number), you may want to print a summary page where they get key information about how you identify the entity they've created and ...



Only top voted, non community-wiki answers of a minimum length are eligible