Sonos app on Mac

As near as I can tell, all they did is run the code through a ‘translator’ to make it native Apple silicon friendly, they didn’t add or subtract anything in the process. 

I can’t figure out why they called the S1 controller “Legacy”. They are already using that name for S2 firmware in older devices. Just to be confusing, I guess.

Heh. As near as I can tell, the people who ‘name’ things are as far from the real user experience as possible, and rarely consider extended support issues. Or use in other places. There’s also a lot of ‘jargon’ that Sonos uses, that’s separate from what we users tend to, well, use. Not assigning much fault there, but sharing of that info might be helpful for Sonos. 

Huh. Lots of ‘as near as I can tell’ thoughts there… ;)

The Sonos interface IMO has gone through three (3) upgrade phases:

S1 > S2 > Sonos App

The latter two incarnations IMO having crossover features besides the fact that users never really adopted the moniker of Sonos App and continued to refer to it as S2.

Sonos is also culpable in the confusion as when one goes into “About Your System” it reads as S2 and not Sonos App.

As far as term “legacy” is concerned to my understanding it only refers to devices that cannot operate on the S2 (Sonos App) controller/Firmware. Furthermore I believe it has to do with memory capacity as well as system architecture that requires more efficient/powerful processors.

Edit:

Maybe some day the app may be called Sonos (App) Ultra 😂😂😂

Somehow I feel like the marketing types are actively working to make it difficult to search for Sonos answers with their naming choices. The "why?" behind their choices would be an interesting story.

The problem with that is: 

System/firmware release notes say this for S2 systems:

And I can find no mention of devices not able to run S2 being called “Legacy”.

We've implemented a new software management strategy that allows us to deliver new features and innovations to our modern Sonos players while continuing to support our older S2 "legacy" devices with essential updates.

Legacy Product Update

And of course, all that leads to the question: Why did they call the S1 Controller update in the OP “Legacy”?

Naming conventions sometimes rise to the most absurd levels.  I once was developing a process to export bar codes to a 3rd party vendor for incorporation into a promotional app.  Like most competent engineers would, I designed it to allow for multiple third party vendors, chosen via a drop down.   The 3rd party's execs flipped out, thinking they were being generic-ised due to the drop down selection being labeled as their company name (yeah, I didn't understand it either).  So I had to label the drop down as something generic, while keeping the internal parameters and output file company specific, all in order to not generic-ise their company's role in the project.

As I said, an absurd level.

It makes sense to me. As I read it Sonos is saying that some products that are S1 and S2 compatible may no longer receive updates to new features that require Sonos App compatibility based upon memory (Click the link you provided). 

In the diagram below I’ve crossed out products that are still S1 and S2 compatible which will continue to receive additional Sonos App feature/updates. For how long only Sonos knows. 🤔 The remaining products will not receive Sonos App feature/updates. * JMHO

 * I manually added Connect and Connect: Amp to match the link Legacy Product Update