FX (sound effect) in UX, is it good practice for systems running on browsers?

Asked

Viewed 47 times

6

I’m doing some finishing for a release, and I had the idea to put some sound effects, like 'crack' when closing modal, or 'pin' by warning something.

Well, personally I didn’t like it, but it seemed intuitive, and I also had the impression that it makes the user more 'friend' of the system, because he gives a few more signals than he is doing.

  • My doubt is the title, apply effects sound interactions is a good practical in systems running on browsers ?
  • If yes, is there a standard preset that is recommended for each type of interaction ? (close, alert, fade, etc...).
  • If it’s not good practice, why ?

Context of my application:

  1. Mobile and Desktop are different applications that do different things, so the effects are just for desktop.
  2. The public/users are very specific, accountants and other people who work in the accounting office.
  3. All users may or may not be wearing headset.
  4. System focus is data maintenance display, processing and automation, not use to perform tasks/obligations.
ux
  • 2

    I personally find it very exciting when software responds to me in this way. It shows me that "someone" took a certain extra care when delivering this application and can often be even intuitive. Now in the technical part, just have to see the question of the context right? It will always run in the browser of a computer? Will run mobile? Will it be accessed in a corporate environment, where the sound is mostly turned off? I find it very valid as an extra, but without dependencies of this functionality. Do you understand? And if you allow me, congratulations on the initiative.

  • 2

    I will give an update on the question with the software context, good notes.!

  • I am not an expert in ux, but I believe that depending on the form used, it becomes rather a good practice. Of course, most of the time, due to the context, users won’t even notice this action, because they probably won’t have the sound of the computer turned on. However, for a visually impaired person, for example, this would be a hand on the wheel, depending on the shape used. So, finishing. Yes, I believe it’s good practice, but like everything else in life, it’s done well. Your example of modals seem to be suitable, but can still be extended to save, cancel, etc. I believe..

  • If it were a question of gamifying an application, it might be interesting

1 answer

2


After some use analysis, it was identified in our context, that sound effects are not so User Friendly as they are in other contexts.

Motives:

  1. Corporate group environment - Users need to communicate by voice with each other through their headsets.
  2. Some users do not use headset and it is not feasible to allow the sound of their Pcs to remain audio.
  3. Maintain a standard between WEB DESKTOP application and MOBILE application, unfeasible to keep FX in one and the other not.
  4. Unplanned functionality at the start of the project, and many changes would need to be made to a not-so-efficient/unnecessary result.

Browser other questions tagged ux

You are not signed in. Login or sign up in order to post.