Sonos CEO steps down after app update debacle

Original Article ↗ Hacker News Discussion ↗

App update fallout

  • Many owners say the new app made previously reliable systems nearly unusable: slow startup, missing speakers, failed playback, unresponsive or delayed volume/track changes, and frequent need to restart or reinstall.
  • Some report being unable to set up or re‑set up older speakers at all, effectively “bricking” multi‑thousand‑dollar systems.
  • A minority say the new app is faster and more stable for them, highlighting inconsistent behavior across networks and setups.
  • Several users mostly avoid the app now, controlling speakers via AirPlay/Spotify Connect instead, or only using the app once for setup.

Legacy hardware, lock‑in, and trust

  • Long‑time customers feel burned by:
    • S1 vs S2 split and dropped compatibility for some devices.
    • Past “recycle mode” that permanently bricked hardware for a discount.
    • New products (e.g., subs) not pairing with older, still‑supported bars.
  • Many vow not to buy more Sonos, or tell friends not to, citing fear that future updates will strand expensive gear.

Technical and architectural criticisms

  • Technical analysis (linked in thread) blames:
    • Moving local control from UPnP-style local APIs to encrypted, cloud‑mediated APIs and WebSockets, increasing latency and fragility, especially on flaky or high‑latency connections.
    • Replacing native UIs with JavaScript-based cross‑platform code.
    • Switching discovery mechanisms and relying heavily on mDNS.
  • These changes are seen as prioritizing cloud control and potential subscription models over local-first reliability.

Alternatives and “dumb” setups

  • Many recommend splitting “smart” from “audio”: passive speakers + amp + streamer (WiiM, Raspberry Pi/Snapcast, Logitech Media Server derivatives, Chromecast Audio/AirPort Express, Roon, Denon/HEOS, Bluesound, etc.).
  • DIY and modular setups are praised for longevity, repairability, and avoiding vendor lock‑in, though acknowledged as more technical.

Business, UX, and leadership themes

  • Commenters debate whether the CEO, board, or engineering leadership is most at fault; some see this as a classic case of enshittification and public‑company growth pressure.
  • The debacle is frequently cited as a case study in:
    • Underestimating software/UX in a hardware company.
    • Shipping a massive architectural change without staged rollout or rollback path.
    • Sacrificing a once‑strong brand and loyal base for a risky platform pivot.