Skip to main content

Simple queue management (adding a song, changing the order, etc) is targeted for "September/October", but seems like such a core function, and at first blush seems like an easy thing to code. Does anyone have an idea why this is one that takes so long to re-engineer? Is the change to store and manage queues on the cloud rather than locally? If so, that seems like an accident waiting to happen, especially for local library users.

 

I was lucky to learn about how dysfunctional the new app was before I updated, so this will be helpful to understand prior to making any changes. Any insight is appreciated.

 Seems like Sonos is not interested in Sonos Playlist creation any more, hence the only queue fix was Clear ( garbage can ).  Hope this is not the case.

 Seems like Sonos is not interested in Sonos Playlist creation any more, hence the only queue fix was Clear ( garbage can ).  Hope this is not the case.

 

https://en.community.sonos.com/general-feedback-and-conversation-229090/is-sonos-abandoning-sonos-playlists-6901558?postid=16780241#post16780241

 Seems like Sonos is not interested in Sonos Playlist creation any more, hence the only queue fix was Clear ( garbage can ).  Hope this is not the case.

It’s a matter of priorities. For example they’ve prioritized Ace features in the app over queue functionality. The features will come eventually they say. It’s ridiculous imo. 

Terms & ConditionsCookie settings