3 ms·
I do use them but not as much as I used to. The main reason is they're not a good fit in a touch-based world. Yes, there are gestures that proxy a hover, but I
by chiefalchemist 7y ago
I do use them but not as much as I used to. The main reason is they're not a good fit in a touch-based world. Yes, there are gestures that proxy a hover, but I don't believe that's the nature of most people usage and expectation - on a touch device or not. That is, using touch so much so often that influences non-touch expectations.
- laurent123456 7y agoSome mobile apps use long press for tooltips. I wish it would become the norm as it's often that I have no idea what a button does, and tooltips would help with that.
- tomlong 7y agoThere's also a pretty long standing convention that long press gets you right click type functionality. It's a difficult thing to be consistent with. For me personally it would be nice if there was a reliable way to detect a quick jab (tool tip), vs a press, vs a long press, but I could see this does not working well for people with mobility issues etc.
- chiefalchemist 7y agoYes. That's the "proxy" I mentioned. But it's not common, and (worse) touch-and-hold is kinda the opposite of hover.
- java-man 7y agoPerhaps on a touch screen device one could use a "help mode" which freezes the UI interaction and displays ballon help over each UI element. Tap the balloon and it expands with more detailed explanation. The help mode could be triggered by a tap on an always present (?) icon somewhere in the corner.
- jrochkind1 7y agoI was gonna post similar... but the tooltips demos in the article are not necessarily open-on-hover. They instead seem to be the kind that appear on the page initially, pointing to a new device and explaining a new feature, until the user dismisses them. I don't believe they involve hover at all. I'm still not personally sure how workable this is on a small screen (because I personally don't have experience with it), and could use some discussion or examples of how this has been done (if it has been done) on mobile. It seems odd to me too to write an article about UX these days without mentioning mobile. But it is worth commenting on the trend of "initially visible tooltips pointing out new or advanced features." Personally, I almost always dismiss them without reading them, they are usually getting in the way of whatever I came to that site/app to do. I wonder if there is public research on their effectiveness.
- chiefalchemist 7y ago> But it is worth commenting on the trend of "initially visible tooltips pointing out new or advanced features." __To me__ those might be tooltips in terms of implementation (i.e., code) but I'm not so sure I would consider them TTs in the traditional sense. They're more like "feature flags".
- jrochkind1 7y agoEither way, they are what the OP is about. I think? They are tooltips in the plain language meaning of the word, they are tips about tools. But I agree the term "tooltip" initially made me think they were talking about the appear-on-hover kind. "feature flag" also means something very different in software discussions, I wouldn't try to re-use it for these. Words are hard. https://en.wikipedia.org/wiki/Feature_toggle https://en.wikipedia.org/wiki/Feature_toggle I might call them "feature disclosure callouts" or "feature announcement callouts" or something like that, but that's a mouthful. "callout" is one graphic design term for that bubble with a pointer annotating the the thing pointed to. https://en.wikipedia.org/wiki/Callout https://en.wikipedia.org/wiki/Callout
- reportgunner 7y agoI think the "touch-based world" brought this lack of understanding of features in the first place.
- the8472 7y agoThat's where a stylus shines.