4 ms·
Conceptually, this is certainly intriguing. Unfortunately, I don't see it as being of much practical use for two reasons. First, with internationalization, you
by crazygringo 6y ago
Conceptually, this is certainly intriguing. Unfortunately, I don't see it as being of much practical use for two reasons.
First, with internationalization, your carefully selected label widths will be destroyed anyways. Because translated strings frequently take up more space, you should always be designing your interfaces with plenty of extra room/flexibility anyways.
And second, with the idea of bolding on hover -- that's really not a great UI pattern to begin with.
From a fundamental design point, bolder strokes require more separation between them, which is why fonts are generally slightly wider as they go bolder. These "uniwidth" typefaces just look uncomfortably squeezed. It's aesthetically not a great solution.
Rather than bold-on-hover, better hover effects include lightening/darkening, underlining, outlining, highlighting, inverting, etc. But if for some reason you're absolutely determined to bold on hover, then just use some layout magic to accomodate expanding the width of the label (likely centered rather than left-aligned, if in a horizontal list) without disturbing items around it.
I will note, however, that fonts often ensure their numerals and certain punctuation remain the same width -- Times New Roman's letters change width if bolded, but its numerals do not -- as it's common to have certain rows in a financial report be bold, and you don't want the numerals to be misaligned with non-bold lines. So numeric tabular data seems like the main use case here, really, which fonts already help take care of. (If you have lots of tabular data with letters and need bold, then you should just be using a monospaced font.)
- yreg 6y agoYour first argument applies to large apps that need to be localised to many languages. It's a non-issue when you are creating say a web for a local small business or an app with just a few views.
- sitkack 6y agoIt also doesn't apply for the main example from the article, that given any string, making it bold or italic doesn't change its width.
- saurik 6y agoYour internationalization issue makes no sense at all to me: this isn't about making everything the same width, as these are explicitly proportional fonts... the mechanism is merely that if you have an italic or bold version of the font that you won't get weird "popping" or layout changes. You are also slamming hard the idea that this would ever be interesting, and yet almost every single communication app I've ever used has chosen to use bold to mean "unread", and it definitely makes sense that if you click on something to read it it shouldn't pop or cause a layout change.