As the title already says.
I don’t get why such a feature would not be available to users.
Now as it stands, every time I search for a song I can only play it which starts a new mix/playlist.
Only option I have is to add the song (I searched for) to my favorites or to an existing playlist, or I can start a mix / playlist from the song. How does this make sense to anyone who develops this app ?
Deezer, do you even read your feedback?
Answered
Why does the web app not have a play next / add to queue button ?
Best answer by Nina Nebo
Hi
On Deezer web app if you click on 3 dot (which is by every track) then you can add song in Listen next or Add to queue .
www.deezer.com
+1Are you casting your audio to a Chromecast device? There’s a 5+ year old bugreport for that:
MrHaroldA wrote:
Are you casting your audio to a Chromecast device? There’s a 5+ year old bugreport for that:
No, listening to music in Firefox browser.
1 person likes this
+13- Deezer Legend
Hi
On Deezer web app if you click on 3 dot (which is by every track) then you can add song in Listen next or Add to queue .
www.deezer.com
💜🎧 | My neighbors listen to GOOD MUSIC whether they like it or not | 🎶💜
1 person likes this
Hi
it doesn’t work when you launch a “pre generated“ playlist or whatever you want to call it which is launched when you play the first track or artist you’ve searched for. I don’t know how to explain it, the developers made this too complicated to use or even explain to someone.
It works on your already existing playlists or albums.
Cheers.
How is having basic funtionality like picking the next song you want to hear something that’s been deemed sometimes not wanted by design for years?! Using an analogy of a car, do you want the blinkers to only work when turning left? Do you enjoy using an elevator, but only when it’s going down, with no ability to go up? This is what your app feels like for a new person coming from Spotify or Tidal. If you were to buy a new car, and have the AC work only at night, you’d surely return it and deem it faulty, while being dumbfounded at the engineers claiming it’s designed that way. How does your product differ from the above examples in case of queuing the next song? Is it the case that you decided not to implement this funcionality because your developers can’t implement it correctly in your codebase?
1 person likes this
+1manioo8 wrote:
Is it the case that you decided not to implement this funcionality because your developers can’t implement it correctly in your codebase?
I think that’s the only correct answer.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.