Did you find this article helpful?
What happened to "Add to Queue" and what's up with "Add to Up Next"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here's the situation. I'm using the iOS app on an iPhone. I have selected an album and am happily listening to it. Mid-album, I decide I want to queue up a new album, for a seamless transition at the end of the current album (maybe I'm about to start driving or running). In the past, the app had the ability to simply queue the next album via "Add to Queue", and it placed the new tracks after the end of the currently playing list of tracks. This is what I'd expect for a queue, and seems sensible.
However with the current version of the app (and it's been like this for a while now), it seems that "Add to Up Next" inserts the new track (or album) directly after the current song! No longer does it place them at the end of the currently playing list of tracks. This breaks up the current album into two parts, with the next album stuck in the middle. I can't imagine this is very useful most of the time.
It is also inconsistent, because if I then add another album, it will place it directly after the end of the second album (still in-between both halves of the first album!). If it's going to be awkward it could at least be consistent!
However, if I remember all this up front, I can start my listening session by selecting my first album using "Add to Up Next" (rather than just selecting the first track of the album), then skip the first track (which will be whatever I was listening to last time) and then I'm happily listening to my first album, and selecting "Add to Up Next" will put the new tracks on the end of the currently playing list. So it's a valid workaround, but it requires forethought and is ugly from a user experience point of view.
What am I missing here? Is the Spotify app user experience broken in this regard? Does anyone know why Spotify changed this? There are valid use cases for queueing a track to play "next" and "after", but the interaction for both cases is inconsistent.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page