This Ars Technica article discusses just how much the rushed release of the new Sonos app will hurt their revenue, but I'm particularly impressed that their first example of its failures was "accessibility features", and that text links straight to @JonathanMosen’s blog post. I'm trying, but I just can't make myself feel too bad for them. And they still have to show they can actually get back on track.
Sonos’ $30M app fail is cautionary tale against rushing unnecessary updates | Ars Technica https://arstechnica.com/gadgets/2024/08/app-redesign-blowback-will-cost-sonos-up-to-30-million-ceo-says/
@simon @JonathanMosen I don't feel bad for them one little bit. Not only did they fail to do things properly, they doubled down and actively chose to ignore early user feedback. That failure is entirely on them and it was entirely preventable.
@simon @JonathanMosen Still, as you say, the more important thing is where they go from here. To be fair to them, they've at least recognised the failure and are apparently putting other things on hold in order to resolve it.
@jcsteh @simon @JonathanMosen yeah I recall the word brave, or something similar being used in response to feedback that this was going to be a problem. I hope they feel exceptionally good about their choices now
@simon @JonathanMosen Someone should do a case study, particular to accessibility, on how not shifting left wound up hurting them in the end.
@simon @JonathanMosen I don't feel bad for them at all. It shows how rushing can be costly. No doubt a few people have lost their jobs over this too.