[android][ios] Deleting a bookmark needs an undo #4547

New issue

Closed

opened 2023-02-20 02:45:01 +00:00 by thany · 0 comments

thany commented

2023-02-20 02:45:01 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.
When accidentally mispressing the screen and deleting a bookmark, I may have no clue what I just deleted. Or I may have deleted something that I put a lot of work in, figuring out whatever it is I need to write in the description field to help me on my way.

The bookmark will be deleted without confirmation, and permanently without the possibility to undo it. This is an antipattern - a destructive operation needs at least either.

In short - a bookmark is silently and permanently deleted. Everyone knows the feeling of accidentally deleting something without the possibility of ever getting it back without recreating it. It's a horrible feeling.

Describe the solution you would like
Either or both:

Confirmation before deleting
Undo deleting a bookmark

Describe alternatives you have considered

Don't use the app while on the move, when it's easier to mis-tap the screen.
Don't use the app while feeling weary, drunk, having a headache, with blurry vision, or when distracted.
When consciously NOT tapping the delete button, be very particulate about staying well away from it, as touchscreens can register a tap at the lightest possible touch that a human would not register one at.

Additional context
This is a problem in both contexts:

In the bookmarks list, holding a bookmark, a menu appears: share, edit, delete. Here, the delete button is close to edit, but also close to the Android back button.
When selecting a bookmark on the map, a menu appears: route from, delete, route to, share. Here, the delete button can be pressed accidentally from all 4 sides.

In both these situations, a bookmark is silently and permanently deleted. So from a UX perspective, I would almost outright call this a bug, and a pretty severe one at that. But technically it's a feature. But I would probably register it as a pretty darn critical one still.

**Is your feature request related to a problem? Please describe.** When accidentally mispressing the screen and deleting a bookmark, I may have no clue what I just deleted. Or I may have deleted something that I put a lot of work in, figuring out whatever it is I need to write in the description field to help me on my way. The bookmark will be deleted without confirmation, and permanently without the possibility to undo it. This is an antipattern - a destructive operation needs at least either. In short - a bookmark is silently and permanently deleted. Everyone knows the feeling of accidentally deleting something without the possibility of ever getting it back without recreating it. It's a horrible feeling. **Describe the solution you would like** Either or both: * Confirmation before deleting * Undo deleting a bookmark **Describe alternatives you have considered** * Don't use the app while on the move, when it's easier to mis-tap the screen. * Don't use the app while feeling weary, drunk, having a headache, with blurry vision, or when distracted. * When consciously NOT tapping the delete button, be very particulate about staying well away from it, as touchscreens can register a tap at the lightest possible touch that a human would not register one at. **Additional context** This is a problem in both contexts: * In the bookmarks list, holding a bookmark, a menu appears: share, edit, delete. Here, the delete button is close to edit, but also close to the Android back button. * When selecting a bookmark on the map, a menu appears: route from, delete, route to, share. Here, the delete button can be pressed accidentally from all 4 sides. In both these situations, a bookmark is silently and permanently deleted. So from a UX perspective, I would almost outright call this a bug, and a pretty severe one at that. But technically it's a feature. But I would probably register it as a pretty darn critical one still.

👍 2

This repo is archived. You cannot comment on issues.