Where actions live
A thing’s actions live on its page. Confirmation, when needed, is a Dialog; feedback shows in place.
On this page
The rule
Everything you can do with a thing lives on its detail page: edit, pause, delete. The person opens the schedule and finds every possible action on it right there. No action gets a page of its own.
Tap Delete: the confirmation is a Dialog in the middle of the screen; once confirmed, feedback shows on the card itself, with the notice right above it.
Does it need confirming?
| When | What |
|---|---|
| The action can be undone, or only changes what the person sees right away | No confirmation: do it, with feedback in place. Always asking teaches people to hit "yes" without reading. |
| Big effect or no way back: delete, pause everything, leave without saving | A Dialog in the middle of the screen that only closes with an answer. |
| Deletes a lot at once | The Dialog asks you to type a word before the button lights up. |
Do and don’t
Do
"Delete" on the schedule page, next to "Edit", opening a Dialog.
All of the thing’s actions in one place.
Don’t
A whole page just to ask whether it may delete.
Takes the person away from where they were, for a one-line question.
Do
To act on many at once, selection in the list itself, with the batch actions on top.
Batches live in the list; one item’s action, on its page.
Don’t
A trash icon on every row of the list.
One wrong tap deletes the wrong row, far from the page where the person sees what is being deleted.
Components
- Dialog: the question before the action.
- StatusOverlay and Notice: the feedback, after.
- Table, with batch actions, for many at once.