3 ms·
With due respect to pg, HN's UI is not something to aspire to, though it has subtle things that make the difference between "meh, but usable" and "omgwtf". The
by potatolicious 14y ago
With due respect to pg, HN's UI is not something to aspire to, though it has subtle things that make the difference between "meh, but usable" and "omgwtf".
The problem I've found with Windows 8 is that there is no visual difference between clickable text/icons and nonclickable text icons. The whole experience comes one of trial and error where you tap on random things like an idiot to see what elicits a response and what doesn't.
The web's way of solving this problem is by underlining text that can be clicked. HN violates this in many places, but at the very least text links underline when moused over - not ideal, but works, and is something that doesn't exist in touch-land.
Ditto, we've been using rollover effects for years to demarcate clickable icons from the unclickable. This entire strategy is now kaput thanks to touch.
We don't necessarily have to have drop shadows, but what we do need is a consistent and unambiguous language that clues the user into how the UI operates. Windows 8 currently lacks this in a really, really bad way. We can do this without skeumorphs, but we still need to do it.
And therein lies the greatest problem with this flat design trend - many designers are going flat without remembering that skeumorphs carry a lot of user hinting that you have to replicate.
- kmfrk 14y agoHn is also aimed at an audience who's HTML heuristics are perfectly honed to detect a link, whatever it may look like.