What a Swipe-to-Delete Action Needs Besides the Gesture Itself
A list row supports swipe-to-delete as the only way to remove an item, with no visible delete icon anywhere on the row.
Per this subject's gesture-discoverability guidance, what's the core problem with shipping it this way?
The correct answer is "Gestures aren't discoverable, so it needs a visible fallback affordance."
This subject's core caveat on gestures is that they are fundamentally not discoverable the way a visible button is — nothing about a plain list row looks like it responds to a leftward swipe, so a first-time user has no way to know the gesture exists unless they already know the convention, stumble into it, or are told. For an important action like delete, the subject names a visible fallback affordance (a delete icon in an overflow menu or edit-mode control) as the more reliable of the two accepted mitigations — the swipe becomes a shortcut layered on top of it, not the only path.
The distractors get the guidance backwards: swipe-to-delete is explicitly not treated as universally learned or low-stakes in this subject — the table marks it as needing a fallback specifically because it's an important action; a missing confirmation dialog is a different, unrelated problem from discoverability; and an onboarding hint alone is called out as scaling poorly as the only solution — users who skip or forget it are back to square one, which is why it's paired with a fallback, not used instead of one.
Share this question