Retired Sonos Staff

Interview

Sonos App Redesign AMA

Forum|Forum|2 years ago
May 14, 2024
770 replies
65998 views

The New Sonos App - Community AMA Recap post is now live!

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.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

B

Bliss752

Lyricist II

Can you describe what the user stories were that you intended on capturing with the app at launch??

R

rmd

Lyricist I

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.

Things You Should Never Do, Part I

M

MattMC

Lyricist II

The lack of responses from Sonos staff concerning accessibility are quite telling.

S

Scotteaton

Lyricist I

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.

“Cross fade”. Does this mean “dump all the things that everybody uses every day, and then release it”? Please don’t use market jargon words on us. Treat us with some respect. AND LISTEN TO US. It’s not all about you.

They were getting cross faded in the office probably, too high to think straight unfortunately

M

Mr Omneo

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 hockum new age mumbo jumbo claptrap is this for an answer? I see a word salad that ignore the question. “Here’s the app, take it or well, we don’t care what you do, we’re doing what we want.” is what you might as well have said.

It’s great that you thought to include us at the start of what is going to be a looooong journey, but you might have leaft us with a usuable product until you got to the first milestone.

C

cpalmer74

Prominent Collaborator I

Do you think it’s fair to put you in front of this crowd?

I mean, they don’t appear to be actually putting anyone in front of this crowd at all...

Yeah, my mistake.

D

Derrick Kaleta

Enthusiast II

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?

Cleary, the prior App was “finished”. So we got this half baked garbage app and are now subject to business jargon that is supposed to make us happy.

D

domotech

Lyricist III

FOLKS, IF YOU ARE LOOKING FOR ANSWERS, YOU WON’T FIND THEM HERE. MAINLY EXCUSES AND INCOMPETENCE.

U

umiami91

Enthusiast I

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.

Okay - I was one of the original questions. And I get that, but losing features suggests rollout was driven by something other than providing an excellent product. This isn’t personal and not an attack on any one person. I just don’t get why you went with a CALENDAR-DRIVEN release versus an EVENT-DRIVEN release. I suppose that’s your prerogative, but going from a nearly bulletproof system to something that doesn’t work at all half the time isn’t useful to me. I just want my speakers to work as something more than an AirPlay speaker.

Y

Yar

Lyricist I

Final nail in the coffin. I will be moving to Roon, so I am not tied down to a single manufacturer.

I will be flogging my equipment on ebay if any of you are interested. This shower of sh!t are a disgrace.

Actually roon (and MediaMonkey, USB Audio Player and others) will play through Sonos speakers. I almost never used the old Sonos app and have no plans to use this new dog's breakfast. Keep the speakers, ditch the app.

Show more replies

Diane

Kate

Tucker

Sign up

Login to the community