He promises frequent improvements through the fall.

I mean, he’s not wrong that the app wasn’t ready. Which begs the question why they didn’t un-roll-it-out. >.>

  • kibiz0r@midwest.socialEnglish
    12·
    4 months ago

    It’s not that simple. They sold new hardware that claimed app support, and the app support was only in the new codebase.

    • fartsparklesEnglish
      1·
      4 months ago

      Ship a new app then. Sonos already do this for older products.

      • kibiz0r@midwest.socialEnglish
        3·
        4 months ago

        Having been in this position, I’m sure having two apps is hell for them and increasingly complicated the more the features and back-end services overlap. And there would probably have been drastically more overlap between v2 and v3 than v1 and v2.

        Ultimately, you just wanna be on one codebase.

        I’m not saying this is a good or okay move by Sonos as a company to their consumers. But the die was cast when the product roadmap was established, and the short-sighted technical solutions people are throwing out in the comments are far worse options for the company (and consumers, in the long run) than just accepting the current problem and moving on.