Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

This question already has an answer here:

For example, imagine if your web application offered inline installation of a Chrome extension. If that installation should fail because of an issue with the Chrome Web Store or Chrome itself, you're likely still going to want to offer the user whatever explanation and advice you can. In doing so, as a nicety should you include an apology for the inconvenience the user is facing? Or is that confusing the issue?

Today's Internet software (as well as hardware) is so interdependent that there are a myriad of situations where such a situation can arise (and especially around the use of APIs).

share|improve this question
add comment

marked as duplicate by Mervin Johnsingh, Charles Wesley, JohnGB, dhmholley, alexeypegov Mar 6 '13 at 18:58

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

2 Answers

It's nice to have an apology, but I'd make it clear whose/what's fault it is.

Sorry, but it seems that Chrome has failed to install the extension because {reason}. Make sure to update to the latest version of Chrome.

share|improve this answer
    
Whats your justification for this ? –  Mervin Johnsingh Mar 6 '13 at 16:51
2  
You wouldn't want the user to blame your product if it wasn't at fault. Making it clear that what went wrong wasn't your product's fault would help the user understand and hopefully prevent a bad user experience. –  Sanaco Mar 6 '13 at 18:40
add comment

Yes, it should. The reason is kind of the other way around of simple user experience. It's not like that having a customized apology makes for a better user experience (it might and not). However, NOT having it could and would very well definitely lead to bad user experience.

For example, say you were the owner of Chrome. Most chrome extensions developed by 3rd party do not have proper error message handlers put in place. So when the error occurs, either the tab/extension/page goes awry, or they show a stacktrace(). () THIS, even though is not the fault of Chrome would most definitely make for a bad user experience and the not so tech savvy user (which would be 80% of your population) would blame Chrome which obviously you wouldn't want.

Hence, it is nice to have the apology not for a better user experience necessarily, but rather to prevent the bad experience.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.