Skip to main content

Today is the day of the AMA!

The new app design has been out for a week, and most of you have had a chance to get used to the new UI.

Some of you might have questions when you have had a week to get to know the new Sonos App interface. Because of that, we want to give you all a chance to ask some of the people who were integral in its creation and design, the questions that have come to mind while you have used the app.

As we mentioned in the event.

Our panelists will be:

  • Diane Roberts, Senior Director of Software Development
  • Kate Wojogbe, Senior Director of User Experience
  • Tucker Severson, Director of Product Management

It will be hosted on the 14th of May from 11:00 until 14:00 GMT -07.

But instead of me telling you what they do and what their role with the app update has been, here are their own introductions:

 

Diane

Diane Roberts is the Senior Director of Software Engineering and Product Management at Sonos responsible for the Sonos Apps. Her group of cross-disciplinary teams build Configuration, Control, and Content experiences on a foundation of Core mobile application technologies. She received dual Bachelors’ of Science in Computer Science and Music from WPI. Diane holds 6 granted patents as a co-inventor.

 

Kate

As Senior Director of User Experience, Kate leads the UX team responsible for Sonos’ home audio hardware, software, and app user experiences. This includes user interfaces on speakers and soundbars, setup for hardware and services, first and third party content experiences, and a variety of methods of control of the Sonos system. Kate graduated from the University of California Los Angeles with a Bachelor of Arts degree in Design.

 

Tucker

Tucker Severson is the Director of Product Management and leads the PM team responsible for the Sonos Apps. Tucker received his BA from Bates College and his MBA from the University of Vermont.

 

We will do our best to answer as many of your questions as possible within the 3-hour window, but we can’t promise to answer every question, especially those you know we can’t discuss.

But if we see a question repeated or a reply getting a lot of likes, don’t worry. We will prioritize those to ensure that many people get the answers they seek.

 

Remember, we can’t talk about things on the roadmap - but if you have questions or feedback about the app redesign, want to know more about our panelists, like their background or favorite band, then the sky is the (cough cough.. NDA) limit!

Thank you, everyone, for participating. We covered as many of the most asked questions as possible. We know tracking the responses wasn't as easy as we had hoped. But we wanted to let the community air frustrations and have their questions answered.

I got a lot of DMs during the AMA, and I will be sure to answer them when I can. Thanks for reaching out!

Keith and I will work on recapping all the questions and feedback we have responded to, and we will update the post here when that is complete. If we didn't get to your question, don't worry. Keith and I are grabbing all the feedback from this thread, even the things we didn't respond to, and ensuring the right people will see the message. This was the first time we created a live AMA in the community, and we learned a lot for future AMAs.

We appreciate all the feedback and questions you gave through this AMA. It helps us understand your most significant feedback and your reasoning. We hear you, and we will ensure the right teams get your feedback. They are listening.

We look forward to rolling out the updates with features (new and old) as soon as they are ready. Keith shared an overview of the timeline for expecting these features to return to the app. Today was the first update, reintroducing alarms and improving the iOS voiceover.

We look forward to seeing your reactions to our future app developments. We hope you all appreciate the work our developers are putting into making the app as fast and easy to use as possible for the general user.
​​

 

 

How about we DM the members of the board of directors? Would that help with this..situation?

Really, I don’t know anymore. 

Good suggestion, contact board members, CEO, Chief Product Officer and send them a link to this AMA session.  Used LinkedIn messages if you have an account.

Mod Edit: Removed links to personal linkedin profiles. We don’t condone barraging peoples private accounts.

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

What a terrible answer. Witty puns are less than helpful. Building an app from the ground up is great, but don’t dump it on users without a choice and without feature parity and call it an upgrade. 

I see someone said they posted the link, but I still can’t find it anywhere on this page. Could someone please just post the direct URL in case it is wrapped in inaccessible content?

 Nice to hang out with you all.. but I have had my fill of fun with these clowns.

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Oh for goodness sake, this answer alone makes me want to never buy another product from Sonos ever again.

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.


I appreciate that, but as I asked in the original question, why didn’t you wait until critical issues were resolved?

When alarms was able to be added back as soon as today, why was the app released when it was in such an incomplete state nearly a week ago? 
 

Today. Sonos APP has a new Update . I just upgraded the app,  but I dind´t seet the alarm I´m looking for it

 

That’s not my point at all 

Will we see numbers re-added to the volume adjusters or is Sonos sticking with this UI decision?

@danull  Yes - volume numbers will be returning to this UI. We are continuing to refine our volume UI based on user feedback and will soon be providing an update to these controls.  Volume numbers should be visible now in the grouping menu.

 

 

 

“Refine volume UI”?  One of the most BASIC functions of music listening.  Turn it up….  Turn it down…  Doesn’t really need refining.

I had senior testing roles with EDS, HP & DXC for nigh on 20 years,  I've seen some shocking s/w in my time but this outweighs them all as you've released a non-working app to your historic  customer community for beta testing.  

Do you not cross check usability against requirements (did you actually have any)? Messages such as a random  "Something went wrong" or "Something is missing" (ellipsis menu) are just not helpful (without even a reference ID)!

Sadly you appear to have a very low opinion of your customers & will lose them if you do not fix this & ideally design a proper app. (not one designed by a technical  illiterate).

I am extremely  unlikely to purchase further SONOS products & will  not endorse your products to friends or family until you fix this mess.

Guys, guys I've figured it out!

The AMA team and the software development and testing testing team are the same!

Clearly they have never attended an AMA to know how they work, and clearly they have never used the Sonos app to know how that worked. 

At least they are consistent 😂🤦🏼‍♂️

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.



Oof, sorry @tuckerseverson , this is not really an answer to the question posed...

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Do you still think you made the right decision?

If Sonos is just using this to log complaints, here are a few:

  • TuneIn - lost custom URLs, which is a must
  • TuneIn - “Favorites” on new app is different than “My Stations” on old app.  Need all my stations.
  • TuneIn - on new app only shows the beginning of station name, with large pointless icon.  For custom URLs, icon blank and I can’t tell one station from the next because they start with the same word (and there is no way to change the name)
  • Qobuz - saved playlists button brings up nothing (playlists missing)
  • Sonos Favorites - shows only a 19 of my 36 Favorites, in a seemingly random order

Basic question getting app to recognize devices is a problem. Or why doesn’t the app work for new users with new equipment. I don’t care about features at this point.

 

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Really BAD decision

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

So we’re not gonna get anything of use here? No apology. No explanation. No accountability. What a joke. 

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Now that it is clear that the new app is not actually ready, what are you going to be doing differently going forward?

 

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Tucker -

Perhaps a better way to phrase the question is: What was the thought process behind releasing the app update when it still lacked parity with significant features that many users relied upon in the previous app? Certainly you have telemetry showing how the previous app was being used?

knock knock… ah you do eventually plan to have dinosaurs on your, on your dinosaur tour right? Hello… knock knock…

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

But why start again? Why not fix problems in old app instead of creating more problems!?

Guys, guys I've figured it out!

The AMA team and the software development and testing testing team are the same!

Clearly they have never attended an AMA to know how they work, and clearly they have never used the Sonos app to know how that worked. 

At least they are consistent 😂🤦🏼‍♂️

Hahaha. Very true. This is terrible. 

As an Android user almost as long as I have been a Sonos user (seventeen years!), so many features were removed from the Android app:

  • The notification that let you quickly pause or resume playback was removed. When the phone is ringing, or someone wants to talk to me, those 10 seconds are agonizing. I now have to launch the app, wait for it to load, wait for the screen with the room I’m in to load, and only then can I pause.
  • The home screen widget that allowed quick pause or resume or to see what was playing was removed.
  • The lock screen notification of what was playing was removed.

When can we expect this regression to be addressed?

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

So you’re saying to willingly decided to give us an app with missing previous features that is broken? The complaint here is that there was regression, not progression. 

What was the thought process behind releasing the app update in an obviously unfinished state, instead of waiting for critical issues to be resolved?

Thank you @veryblocky @YorkSteve @umiami91. Since you all had similar questions, I’d like to answer them together.

An app is never finished! 

It’s probably a good idea to give you some background. This is a new app - we started from an empty project file. As the project progressed, we stopped investing our time in the old app code. Over time we “cross-faded” our engineering attention into the new app. We need to make the new app be the app going forward so we stop splitting our attention.

We decided that now is the moment to bring you the new app. This is the beginning, and we will be continually iterating going forward. As I said - an app is never finished.

Yes, but most are functional.  What a cop out of an answer, honestly.  I’ve rolled out software before and not admitting this was a total debacle is outrageous in its face.  
 

Your decisions have repercussions and those will probably be people abandoning your fragile ecosystem after having given you thousands of dollars.  If that’s how you want to deliver to your shareholders that’s your business, but I’m done co tributes to it.

Terms & ConditionsCookie settings