I don't think there was malice involved. Sonos seems like a company that has a very tough time making money, and since they IPO'd two years ago they are "responsible" to shareholders now (their stock opened at 15 and as of Oct 2 it was 15 -- could be worse!). Bricking old products would give a profit boost if everyone said ok and bought new products, but they underestimated the backlash.
It's the same reason their client sucks -- it will cost a lot of money to make native apps that take advantage of the respective eco-systems. The client suffices for most people so why bother?
That said, I'll go back to being pissed if they release new hardware I want and get rid of the 30% discount.
Open-source the last compatible version of the client and let the community maintain it? Or at the very least publish the API specification and let the community build a new one from scratch?
https://github.com/pascalopitz/unoffical-sonos-controller-fo...
Open sourcing the old version of the software might be too much to ask for various reasons, but publishing API documentation in order to enable third party implementations IMO should be legally required in cases like this.
given Sonos' track record with the "lol, can't have anyone using an OLD PRODUCT THAT STILL WORKS FINE" thing i'm rather unsure we should really give them the benefit of the doubt here
ref https://news.ycombinator.com/item?id=21895086 for "recycle mode" fiasco