3 ms·
I wonder if we need a new UX pattern where every single destructive action is delayed by ~30s such that there is ample time to press “cmd+z” or a toast undo but
by haburka 4y ago
I wonder if we need a new UX pattern where every single destructive action is delayed by ~30s such that there is ample time to press “cmd+z” or a toast undo button.
It’s not very difficult to implement the client side code for this, and I think users would appreciate it.
However delaying a “delete” would cause some complications with the local data, where you might want to optimistically render the UI such that the delete went through. That shouldn’t be difficult in any modern state management library though.
- Jerrrry 4y ago>modern state management library with as much time, effort, use, and praise that these get, I would expect every state change / collection to have a corresponding input and action buffer, effectively making all user actions CTRL+Z-able.
- booleandilemma 4y agoHaving an undo button instead of a confirmation button is already standard in several Google apps.
- ChrisMarshallNY 4y agoThe latest version of the MacOS (Ventura) has a delay in sending mail. I haven't timed it, but it seems like about 20 seconds. During that time, there's an "Undo Send" in the bottom of the nav pane. It's a bit weird, but I've gotten used to it.
- colejohnson66 4y agoGmail had that feature over a decade ago. It's helped me maybe once or twice, but it's nice to have.
- cxr 4y agoWe might be better off if conventions in email programs changed so that the "Send" was not the default but rather something like "Schedule this to be sent at the next top of the hour". We wouldn't have to resort to any UI fakery, and there might be interesting societal effects if widespread enough. (Most mail delivery doesn't need to be immediate, but pretty much no one tunes their setup to minimize interruptions.) It obviously won't work very well if it's entirely handled by the client, since your battery might die, you might go out of range, etc.