Description:
In specific app views, performing a long press on an album or track opens the drop-target menu. If a user releases the item immediately at its original position to cancel the menu, the app triggers an unintended action: songs start playing immediately, and albums are opened.
Issue:
This behavior is counter-intuitive and leads to accidental actions. Since the drop-target menu already includes an explicit playback option, releasing the item at its original position should simply close the menu instead of forcing playback or opening the album.
I understand that it may follows the standard OS behavior, but in the specific context of the drop-target menu, it just doesn’t feel right. Even if you don’t intend to select the ‘Play’ option within the drop-target menu and simply want to exit, a selection is triggered automatically upon release.
How else are you supposed to leave this menu without that happening? There is a way, of course, but it’s not intuitive and feels quite awkward: you have to drag and release the item somewhere ‘neutral’ outside the track/album, or drop-target buttons.
I don’t see how this is currently a ‘good solution,’ especially since it frequently leads (me?) to accidental inputs in daily use.
Anyway, I just wanted to point this out as a UX issue (in my opinion).
You’re right, I stand corrected -I didn’t realize that moving the finger slightly prevents the click.
However, from my point of view, that doesn’t really change the confusion. Once the menu pops up, the user’s focus is entirely on the new menu options, not on the underlying track or album anymore. Having to perform a ‘mini-movement’ just to avoid a click still feels counterintuitive in that moment.
But fair enough, I think everything has been said. Thanks for your patient replies and for looking into this! Maybe it’s just me being the ‘weird’ one here .
!
.