Hacker News new | ask | show | jobs
by codemonkey-zeta 1667 days ago
I'm a big fan of this solution, and I've used it quite a few times.

Ideally I would like to use drop downs where possible like GP describes, since a > icon (or similar) before some text unambiguously indicates how to get more information, but sometimes the implementation is non-obvious. I've had issues when my data is tabular (like this pricing page). Where should the drop down appear? Sometimes you have a 3rd party table (or template, like this article describes), and the customization options might not be there. At the very least you have to spend time styling both the additional information AND figuring out how it fits into the document flow.

The great thing about a tooltip is that it's out of the document flow. You can just ignore the rest of your application, resulting in (usually) faster development speed. However, as GP points out, you have to consider mobile, and it's not always obvious how to indicate _in_ the context of your document that something is hoverable.

ⓘ is a best of both worlds solution IMO. It's totally unambiguous on both desktop and mobile that hovering, clicking, or tapping will bring up more information, AND you get the development speed of using a tooltip.