Just lost a potential job today because Adobe has this pathological hatred towards audio. Client likes my design work and creativity, wanted me to design an app that relies heavily on music and audio cues. Couldn't be done on Adobe apps so they went to a developer who charges a lot more and produces uninspired apps (seriously, their lackluster apps were the reason the clients came to me first.)

What do we have to do to convince Adobe that audio is a valid tool for mobile/internet communication? A petition? Crowdfunding bribes? Boycott? Protests outside Adobe HQ? (we'll definitely have the best-designed placards) Many people have asked for sound tools in numerous Adobe apps but we get ignored, so what do we have to do for Adobe to take audio seriously?

In order to prototype multi-modal interfaces, we need the ability to add simulated voice prompts/responses (and sound effects) to screen transitions, buttons, etc. The experience of many applications could be improved/streamlined if the interaction sequences involved a combination of voice and screen.

Yes, please add sound capabilities. As a sound artist wanting to experiment with app creation from a sound perspective, it's frustrating not being able to utilise Adobe in this way.

fully agree - when recording a demo video it is VERY likely, that I also want to add a voice track to my demo, where I can provide some info on what I am doing in the demo. At the moment, I have to do a demo recording and sound recording in parallel and then put together both recordings in a video tool (or I use a video tool instead, that supports screen and voice recording instead of using the XD video recording (both is not very user friendly)

Yes please! The ability to do voice over when demonstrating a prototype and sending the MP4 to others would be so good.

I think this could be a fairly easy feature to add: when in Prototype mode and a user makes an interaction between two artboards/widgets, in the dropdown menu that appears to customize the interaction, the user should be allowed to attach a sound to the interaction or to just be able to attach a sound as an individual widget interaction when clicking on it.

This is important because if we are designing for impairments or users who are auditory learners, our prototypes should be able to reflect the full capabilities of what we are imagining our designs can do for those users. For example, there are apps designed for education and that give instructions, so if our users prefer to hear while reading the instructions, we should be allowed to attach a voice to the prototype so the users can understand how the designs can help them.

Would be a great feature and to be used on so many occasions!

Yes. Please add sound to this. I could use this to help my English Language Learners. Right now I have to try and create flash files using Adobe Captivate so that my students have interactive stuff. With sound and Adobe XD, I would be unstoppable! I mean, sound is a YUGGGGE part of the UX.

Yes, sound please! Remember we're not just doing website prototypes here; mobile apps rely (or should) heavily on sound.

Here's a great talk on it:
https://developer.apple.com/videos/play/wwdc2017/803/

Please support sound events!

Wouldn't it be great if we could add sounds to interactions in prototype mode? After all sound is a big part of user experience too. Along with micro animations, sound can give a prototype that little extra bit of polish and make it feel more like a finished product.

Here is a great article I read by Henry Daw on the subject. http://www.awwwards.com/being-smart-with-sound.html

I had an idea about adding the abillity to add background music even when you switch to a new artboard, so I can create a screen by screen game. That means that I move the player by clicking on the arrows that will be displayed on screen. Every step of the player is a loose artboard with a different backgroud that consists of a jpg image. I would really appreciate that. Sorry for my bad spelling. I am from The Netherlands, so sorry for that.

They should allow it and people who wants to use it should use it

Some sites audio is good others no, even on the Adobe site audio is low and muffled. Believe me I've tried about everything. Everything sounds wise works fine on my computer it's just on the internet I have problems.

Whenever I bring this subject up people always respond with "there was this one annoying web site some years ago" as definitive proof that Adobe is the protector of all that is good and decent on the internet and should be rewarded for their campaign to wipe out all audio from the internet. Well, I heard a bad song last year, so why doesn't Adobe go after music with the same fanaticism? Also there are misspellings and bad grammar on a few web sites, so why not outlaw text? While we're at it, I've experienced far more badly drawn artwork than I have too-loud audio files, so shouldn't Adobe eliminate all graphics as well?

If you don't like sarcasm, tough. I've tried to be polite and respectful but Adobe completely ignores me so I'm trying something new.

One last thought: have you ever considered the possibility that noisy web sites are so bad _because_ Adobe refuses to apply any standards or proper tools? You think that just maybe if Adobe added the same type of audio tools as they do graphic and text tools we might not have to deal with crappy third-party sloppy fixes that never work right?

OK, I'll admit I had to look up "Misophonia". That done, the post above was clearly written at the apogee of someone's frustration —but the point *is* good, and it's odd that it has had to come to this. I leave sound off my Web-pages for pretty much this reason, and I have certainly met sites whose use of sound needed improving, for example a check-box that reads "Do not start playing A/V content, very loudly, ten minutes after this page has been opened."