Perhaps your browser suggestion should include this useful info. It's one thing to say this as a blanket statement to people using old IE versions and having trouble--or as a recommendation on a site people need access to--but when trying to show off a thing among a group who make pretty intentional decisions about what browser to use it's just going to make people shrug and move on.
FYI The smiley only makes it worse. Brad Frost has recently written a post about how important it is to write user-friendly error messages ( https://medium.com/@thomasfuchs/how-to-write-an-error-messag... ). If Chrome is required, at least tell me why.
No, because I don't normally use that browser. So, I guess the user doesn't get to know why, will just ignore the site and move on to something else.
I do actually know, but I'm pointing out the major problem from the user's perspective. If a everyday non-technical person visits, they're just going to assume the page is broken. You usually only get one (very short) attempt at getting the user interested enough to interact with your site.
They should be displaying the simple explanation why their site won't work on Firefox, IE, Safari, Opera, etc.
11 comments
[ 5.5 ms ] story [ 45.6 ms ] threadFor those of you, like me, who don't use Chrome, this post appears to have some samples of giftawk output:
http://thenextweb.com/apps/2015/08/19/a-true-gif-t/
:( Please avoid lock-in
Nope.
I don't care then.
No, because I don't normally use that browser. So, I guess the user doesn't get to know why, will just ignore the site and move on to something else.
I do actually know, but I'm pointing out the major problem from the user's perspective. If a everyday non-technical person visits, they're just going to assume the page is broken. You usually only get one (very short) attempt at getting the user interested enough to interact with your site.
They should be displaying the simple explanation why their site won't work on Firefox, IE, Safari, Opera, etc.