SONOS are you reading this? Please put the controller queue function back how it was!

... Just offering a different perspective to illustrate that the whole Sonos user community is freaking out about this change. And, I'm still recommending the system to friends and family.

Not quite. I like the new system as it offers more pluses than minuses - as progress always does. A few transient lost queues (I've always saved queues) in the learning curve and that was that. A new user would know nothing else.
If you count the number of different posters who hate this change they are, well, very few. That does not denigrate or ignore their opinions on the change.
Will it change back. Two months on....of course not. Imagine the protests.

... Just offering a different perspective to illustrate that the whole Sonos user community is freaking out about this change. And, I'm still recommending the system to friends and family.

Not quite. I like the new system as it offers more pluses than minuses - as progress always does. A few transient lost queues (I've always saved queues) in the learning curve and that was that. A new user would know nothing else.
If you count the number of different posters who hate this change they are, well, very few. That does not denigrate or ignore their opinions on the change.
Will it change back. Two months on....of course not. Imagine the protests.

Rolling back the update is by no means the only option here. As I have said here a few times you can give users a customization option which allows users to keep queue management as it currently is or as it was previous. This has been successfully done by SonoPad/SonoPhone - a 3rd party controller. I personally think that works very well.

Then you get two polarised sets of users IMO.
A big complaint is about when people throw parties. Some guests are likely to have Sonos. Which version will they try to use - back to babysitting, as some have called it, your guests.

The current system needs more work on it to iron out some of the wrinkles. Why not seek to improve the current experience rather than being firmly stuck in the, controversial in its own right, past and be positive about direction.

Wouldn't, say, an undo button (for just one movement forward, be of more benefit than toggles.

Honestly if there were just a toggle to disable clicking on a song it would alleviate 90% of the issues. Make it so you can force people to use the ... simple for those who use it other places to realize one click on mine is disabled.

But that toggle, Chris, would still introduce two different users.
As you know, I like the one touch - it's not perfect but...neither was the old version. I haven't "lost" a queue for what...say...six weeks now and only before because of my inattention.

Where things are inserted in the queue is far more important than an "old way" toggle.

But to those users that want to disable that the n their own have home it can be easily explained as being in a secure mode to avoid music interruption. If someone wants it in a secure mode it can be their option. I think lack of personalization will eventually become more of a hindrance to Sonos sales vs an asset.

Then you get two polarised sets of users IMO.
A big complaint is about when people throw parties. Some guests are likely to have Sonos. Which version will they try to use - back to babysitting, as some have called it, your guests.

The current system needs more work on it to iron out some of the wrinkles. Why not seek to improve the current experience rather than being firmly stuck in the, controversial in its own right, past and be positive about direction.

Wouldn't, say, an undo button (for just one movement forward, be of more benefit than toggles.

I honestly don't understand this talk about "polarized groups". That casts an unnecessary negative cloud on a request to customize. I have no issue using the queue in my preferred way and you doing the same. For me to understand your point you need to present the argument for the downside in allowing different use cases. I personally see no concern. SonoPad presented 4 queue management options - I picked one and scarcely think about what the persons may be doing. This would be to create a problem where none really exists. But again please explain what is the real issue with the customization you are seeing.

I was sure I had answered this somewhere but I can't find it. What happens is that the end of playing a queue, no matter where those tracks came from, the focus of the player rotates back to the first song so that you can restart what was playing with just the push if a button. The downside, is that if you then go to add an album/track/playlist using Play Now, the focus is still at track 1, so these get added at track 2 and beyond.

We've been sure to pass on the feedback that this can be a negative experience to the team so they know to take a look into.

I keep seeing phrases like "tap to play", and I keep trying to reconcile the intentions of Sonos with the current reality of their software. I have a big problem with the current "insert into stopped queue" functionality, because while it's a small thing, it's everything. I can see the logic in hitting "play" and having your selection inserted into a playing queue, but when the queue is expired, an insert makes little sense, you want a "clear and play" or an "append and play". Depends whether the queue is meant to be a persistent (like Sonos 6.3) or ephemeral thing. The fact that the "play" buttons alternate between "insert" and "clear" on different screens suggests Sonos can't decide on queue lifetime. I can deal with the queue being a fleeting thing and losing the ability to check "what was that song I heard yesterday?". Having to manually force-clear the queue just to get "play now" to work correctly is a pain.

Assuming users weren't really crying out for a "play this followed by the last 17 of 18 tracks I played yesterday" button (which is what Sonos currently gives as a default), then the "insert into stopped queue" bug may be as simple as Sonos not differentiating between an expired queue (played-to-end-flag hit or play position is reset to track 1 0:00) and a paused/stopped queue (pause button hit, play position is one or more tracks/seconds into the queue).

A response from Sonos would be nice. I might go an play with iTunes/Spotify desktop controllers to see if they're as broken, to try and understand where Sonos are coming from.

@Alan. Where things are inserted into the queue needs more work. To my mind, this a move forward change that needs supporting.