Tom Kell asks why some single taps will start playing track but it takes two taps on the track itself to start.
Is there a reason for this variance to share with Tom? Or is this something we will seek to change in an update?
Thank you.
Tom Kell asks why some single taps will start playing track but it takes two taps on the track itself to start.
Is there a reason for this variance to share with Tom? Or is this something we will seek to change in an update?
Thank you.
I think this is another one of those âalways been this wayâ things. I assume the doubleclick idea was this would protect folks from accidentally turning on a song while scrolling on mobile.
However, it seems that other music players allow single click of a song title to turn it on, and it doesnât cause problems.
Anyone want to go check out how this works across other services? We should use whatever play interface is most common. That will make it easy for folks to try resonate.
My thought too. Iâll relay that.
Maybe thereâs a haptic setting that would weed out the scrolling motion?
Would it be correct to say double-tap is under review, or is this more accurately described as the UX we think works best?
I think double tap is 100% an unnecessary precaution.
I just checked and, despite it being hard to compare 1:1 because it turns out almost 100% of competing offers (Deezer, Spotify, Apple Music, Tidal) use apps on appstores rather than direct web streaming on smartphones, theyâre ALL single tap based.
Also, I just checked if it had any influence when scrolling and it just really doesnât because since the tap is accounted for when the finger leaves the surface in the same area it meets it, thereâs very little chance you tap it by mistake, scenarios :
I start scrolling from top to bottom and end up by mistake on the play button and leave at that exact moment > Since I didnât start pressing on the screen on the play button, it doesnât register as a tap anyway.
I start scrolling on the play button and release at the top of the page > Since I didnât âleave the surfaceâ with my finger at the same spot I pressed it, it doesnât register as a tap either.
At least those are the scenarios I currently experienced on all the websites and apps I just tried on mobile.
I think we can get rid of double tap itâll be a much smoother experience.
Currently, itâs more like a double click feature for desktop. The play buttons only appear on hover state.
Spotify etc⌠makes difficult to use their web apps on purpose.
Yeah Iâm aware why Spotify et al are eager to push you into their closed ecosystem, but other than that, do we think that behavior is necessary ? (play on hover state that is). Does it serve any accessibility purpose? Or are we just being overly cautious.
I was not familiar with this new trend with single tap/clicks to play while not interacting with actual buttons. I see it as an opportunity to create more mess/confusion, especially if in the future we want track titles to link to individual track pages.
Iâd be in favour of adding more affordance to this UI.
Taping once would toggle the play button and or change item background color.
A big button to start/pause playlist would be nice too.
Double click seems good enough for this kind of problem.
I think the trend is more along the line of âthereâs ALWAYS a play button widely visible so that you donât need to click twice to listenâ
Hereâs an example of Deezerâs main page
Itâs similar on most services.
On resonate you need to click on the card first to be sent to a place where you can then click play.
On mobile (iOS) and desktop (firefox on mac), I can tap a track number once and it plays. Tapping on the track name does nothing on mobile and starts the track on desktop.
If I tap on an album cover, Iâm sent to the album detail, then I pick a track. Since the user needs to be able to tap on album covers for the purposes of navigation, this makes sense.
A compromise for the âtoo many clicksâ issue could be to offer a play button on the album cover (like Deezer). If the user taps the play button on the album cover image, the album starts playing. If the user taps elsewhere on the album cover, then it takes the user to the album detail.
Yeah thatâs also my understanding of how things should behave.
If weâre looking to implement âtrack pagesâ (in I guess an effort to make things more like Bandcamp because thatâs how it works there and itâs nice too) then I get that the track isnât a button, in the meantime itâs a bit of confusing UI choice not to have the track name also be a play button.
I must have missed something because even on desktop the name is just regular text for me.
what do you mean by track page? Like this?
recruiting you for the monthly testing squad, what is your browser and OS (to see if i can replicate)?
Actually yes, but I canât access that or a play button on clicking on the title in the album page.
And also this is all a bit weird, like the page you sent has a different UI from the album page where the artist name is unclickable and doesnât direct me to the artist page (I have to go to the footer player to do that).
All things that can redirect to single pages/artist pages etc. should in general be more clickable so that itâs super intuitive for people to wander on the site.
I have several browsers depending on my use cases (so Opera/Firefox/Chrome), here I was testing on Chrome let me check if I have the same behavior on Mozilla.
Yep I do : on album pages clicking the track titles doesnât play the track and itâs just regular text. Just the number (when hovered turning into a play button) allows me to select tracks.
I was able to replicate i think:
Desktop (testing on Chrome)
go to artist page (same is true on track detail, artist page is just example)
case 1: single click on album art + arrow
case 2: single click vs double click on track title text
confusion: unless debugging, it seems unclear as to how many times a user has to click, and on what.
is this a huge issue? canât really know unless the app is counting clicks (is it?). Maybe itâs fine, maybe not.
Woah I didnât even realize the title was actually a button, like when I hover I have the text highlight pointer, but youâre right, when double clicking it apparently is a button still which is very odd. OK.
I agree this is not a huge issue but itâs better to sort it out because if we already had someone being confused about this it means itâll confuse a lot of people especially since it really doesnât fit any web standard that I know of (usually when I can highlight text and donât see the âhandâ pointer, I canât think of a website where a thing is still considered a button) and itâs also not a streaming platform standard so itâs really needlesly confusing for a very low benefit short or long term, that I can think of.
For my mobile (android), tapping twice on the track name starts the trackâŚ
(tapping the track number once, or the play icon once will also start a track)
I believe it was the tapping twice on the name, while only once elsewhere, (in mobile) that the user was calling out for review.