4 ms·
Please note, the article does not seem to actually be about appear-on-hover tooltips that many of us think of when we hear "tooltip". But rather "callout bubbl
by jrochkind1 7y ago
Please note, the article does not seem to actually be about appear-on-hover tooltips that many of us think of when we hear "tooltip".
But rather "callout bubbles" that appear on initial screen display, to point out/explain a new feature (or a feature they want to 'advertise' for some other reason). They usually either stay there until you dismiss them, or until they time out.
I have been noticing these more and more, and I think they are worth commenting upon, I'm not sure this article does a great job of it, starting with calling them "tooltips" that is misleading some people not reading the article carefully to miss what it's actually about, as evidenced in the HN comments here. (To be fair to the OP, they are "tips about tools"...).
One thing I wonder is how effective they are, or if there's any public research on it. Myself, I'd say ~75% of the time I dismiss them without even reading them, as being there on page load (and often covering up other parts of the page), they're getting in the way of whatever I came to site/page/app to do, and have in mind to get done when I see them.
- badwolf 7y agoWe generally call them "coach marks" tooltips as most people know them are a bit of a tricky thing to do on mobile apps. Coach marks/app tours can be great, however apps that have them, but don't have an easy method to skip make me rage!
- jrochkind1 7y agoThere's also the distinction between providing a _sequence_ of them as an app tour (the case where your comment about skipping them is relevant, i think), and providing a _single_ one, to ordinary users of the app who don't know they are taking a "tour", to advertise a specific (usually new) feature/UI device. The OP examples seem to be more the latter. "Coach mark" is a good term, thanks.
- jiveturkey 7y agoagreed to you and GP. i always skip these, due to sensitization to browser pop-ins. they are usually beyond obvious, further rage inducing. when they are actually useful, again still rage inducing because I skipped it and there is generally no way to get the coach tip back. sorry, ad pop-ins have ruined what would otherwise be fairly useful.
- arcturus17 7y agoMy UX professor told us "if you have to explain it, then it's poorly designed"; I think this is right in most cases. That, or it's well-designed, and you're making it superfluous as you're saying.
- jrochkind1 7y agoi think that's a good rule of thumb and something to strive for, and most interfaces can be made more obvious than they are with more skilled design work... but imagine if you applied that rule to, say, an airplane cockpit. Sometimes powerful interfaces for doing complicated/powerful things need to be learned. (And an airplane cockpit can still be designed poorly or well at varying degrees, certainly! A well-designed one will be safer and easier to use. But nobody thinks an untrained person should be able to step into even a well-designed one and fly a plane. That doesn't mean it's a poorly designed interface).
- JohnFen 7y ago> Myself, I'd say ~75% of the time I dismiss them without even reading them This is me, too, although I don't read them more than 75% of the time. I find them disruptive. I've even developed muscle memory so any time I see a "got it" button, I just immediately click it so I can get on with whatever I was trying to do.