Replacing the Sonos App: Essential Functions Disappear
On April 23, 2024, Sonos announced a new mobile and web application for its products. At launch, it deprived users of common features.
How can a redesigned application be launched without removing functions that customers use daily?
Anticipate the usage value of each function before removing it, even temporarily. When 69 simulated voices reacted to the Sonos decision, about four out of five declared against it. Doubt focused first on the company's ability to execute this change without breaking the user experience.
The context, in plain terms
On April 23, 2024, Sonos publicly announced a completely redesigned Sonos application for its S2 mobile app and a new web application. It was scheduled for availability on May 7. The new version was meant to support existing S2 products and replace the Sonos desktop controller with this new web application.
On May 7, the application launched as planned. However, media coverage later reported that the new version lacked several functions customers regularly used. Notable absences included the search function, sleep timers, and other controls users considered essential. The consequences were significant. Reuters reported on January 13, 2025, that Sonos CEO Patrick Spence had stepped down after the app update debacle. This confirmed that the May 2024 launch broke vital user functions. Delays for two product launches followed. The company focused on correcting the application, with remediation costs estimated between 20 and 30 million dollars. Most of the missing functions, over 80 percent, were restored by October 2024.
Publicly, the exact identity of the internal decision-maker or the meeting where the final product decision was made is not established. The official financial impact was reported only as an estimate.
The Gap Between Ambition and Use
On May 7, 2024, the new Sonos app reached customers' devices. For the company, it was the complete redesign announced on April 23. But for customers, that same date signaled the end of features integrated into their daily lives. It transformed an anticipated update into an immediate source of frustration.
Before a panel of simulated voices, the decision met outright rejection. About four voices out of five declared against this application replacement. About one voice out of seven expressed marked doubts. Only a tiny fraction of voices supported it. Among the voices against are accessibility-dependent users, shut out of a system they need.
An application is judged by what it allows users to do, not just by what it promises to be.
What Sonos Customers Lost Along the Way
The main brake identified is doubt about execution. Objections focused first on how this transition was managed and its immediate consequences for the customer experience. The question was whether the company could switch apps without breaking service continuity for its customers.
Opposition crystallized around the absence of basic functions like search or sleep timers, elements considered standard. What these voices describe has a name: Usage Disruption, when a redesign breaks things customers did without thinking. The problem is the neglect of what users have already invested in time and learning in the previous interface.
A blind user on the panel says their screen reader can no longer navigate the app and calls it discrimination. Removing a function creates a stronger absence than adding a new one.
The Panel Engineer Who Sees the Future, Not the Present
Amid this rejection, some voices still supported the decision, two of them from leadership. A simulated lead engineer on the product team, for example, defended the initiative by stating: “The new app is a technical leap forward, and once users adapt, they’ll see the benefits.” This voice expresses confidence in the future and in users' ability to adapt to innovation, even if it is disruptive in the short term.
A simulated CFO also supported the decision, focusing on long-term benefits: “The backlash is temporary, and the long-term savings from automation will outweigh the short-term pain, this was the right call.” These voices, though a minority in the overall panel, show a strategic and economic vision that prioritizes future gains.
We ran the exercise three times: same answer. Technical and financial vision is not enough to offset the immediate loss of use.
Measure How Rooted a Feature Is Before Removing It
For a leader facing a major redesign, the first step is to map the Usage Disruption of each feature considered for removal. This means understanding not only its maintenance cost but also its role in users' daily habits and the dependencies it created. Then, communicate not about what the application will become, but about how the transition will be ensured for each user, especially the most vulnerable.
Sonos had to face the consequences of this usage break. This included its CEO's resignation in January 2025 and the postponement of two product launches. By October 2024, the company had restored more than 80 percent of the missing functions; it put remediation costs at $20 million to $30 million.
What the case does not say is what could have been anticipated if the voice of accessibility-dependent users had been heard earlier. The May 7 launch might then have read differently. Modernization without transition is a break, not an evolution.
What you have just read comes from a rehearsal, not a report. This analysis was conducted on the Kapari test bench, before a panel of 69 simulated voices. The exercise allowed us to hear the panel's outright rejection of the removal of essential functions. It also showed how doubt about execution dominated long-term gain arguments. The same exercise can illuminate a decision your company has not yet announced. It surfaces the objections before the announcement.
The questions readers ask
How can the removal of features be prevented from being perceived as discrimination by some users?
On the simulated panel, a blind user who relies on screen readers describes being locked out of the system and calls it discrimination. For that user, removing functions becomes direct exclusion. Bring these voices in from the design stage.
What is the real cost of an update that degrades the user experience?
At Sonos, the bill came in three parts: remediation estimated at $20 million to $30 million, two delayed product launches, then the CEO's departure in January 2025. On top of direct costs come harder-to-count losses in reputation and trust.
Is this a poll or a prediction?
The voices cited in this article are those of a simulated panel, not the result of a poll or a prediction about reality. The 69 voices are those of this panel, and they do not constitute a measure of public opinion. The reported facts come from dated and verified media sources. Kapari sheds light on the decision; it does not make it.
How Kapari computes and reads its signals: the method
Related cases
Your next decision deserves the same scrutiny.
Run it through the test bench before you announce it: a panel of voices reacts, you read the range and you see the frictions coming.
Start free