Design annoyances
codefastdieyoung.com
Design annoyances
1–10 of 30 posts
Re: Design annoyances
#2I'm curious what others think about #3 (The vertical scrollbar). Traditionally it's considered messing with the defaults of the browser, and wasting precious screen space; but I hear from more and more (graphical) designers that they'd like me to stop the page from jumping by doing exactly this.
Re: Design annoyances
#3Most of these have been pretty well known or obvious, which is why those that do them have little excuse. But I disagree strongly that #1 is a problem. Some things, like the header in his example, usually should be full width. While others, especially columns of text should be of a fixed maximum width to improve readability. Who cares about blank bars to the sides of the screen? Or at least, who cares as much as they do about struggling to read too wide columns of text?
Re: Design annoyances
#4I'm curious what others think about #3 (The vertical scrollbar). Traditionally it's considered messing with the defaults of the browser, and wasting precious screen space; but I hear from more and more (graphical) designers that they'd like me to stop the page from jumping by doing exactly this.
I think it's mostly just the usability perspective, like was mentioned in the article. If you don't force the vertical scrollbar and this causes elements that should be in a static position to move, you've got a frustrating usability issue. (Like on sites that have forward/back buttons that jump around so you can't repeatedly click the same button. How frustrating.)
Re: Design annoyances
#5Number three is interesting, especially if we consider what Canonical have done recently with Unity and moved scrollbars outside the window[1], freeing-up the screen real-estate that they permanently occupy.
[1] http://design.canonical.com/2011/03/introducing-overlay-scro...
Re: Design annoyances
#6I'm certainly more likely to feel like I'm signing up for something magical when I'm faced with big pretty happy-looking form elements! :)
Re: Design annoyances
#7Number three is interesting, especially if we consider what Canonical have done recently with Unity and moved scrollbars outside the window[1], freeing-up the screen real-estate that they permanently occupy. [1] http://design.canonical.com/2011/03/introducing-overlay-scro...
It's interesting how reminiscent that design is of Google Wave's much-criticized scrollbars: the position indicator following the thumb, the page-up/page-down buttons, and the minimalist appearance when not in use. I wonder if Wave's design was just ahead of its time.
Re: Design annoyances
#8The reason for #1 is because fluid layouts can force text lines to stretch on wide screen monitors. As such, the line becomes harder to read.
Re: Design annoyances
#9The reason for #1 is because fluid layouts can force text lines to stretch on wide screen monitors. As such, the line becomes harder to read.
You can always combine a fluid layout with a max-width for your text. Besides its not the width of the monitor that matters, its the width of the windows and I like my windows narrow, thank you very much. I used to be able to do this, but then they went and broke Readability :-(.
Re: Design annoyances
#10Number three is interesting, especially if we consider what Canonical have done recently with Unity and moved scrollbars outside the window[1], freeing-up the screen real-estate that they permanently occupy. [1] http://design.canonical.com/2011/03/introducing-overlay-scro...
It's interesting how reminiscent that design is of Google Wave's much-criticized scrollbars: the position indicator following the thumb, the page-up/page-down buttons, and the minimalist appearance when not in use. I wonder if Wave's design was just ahead of its time.
Wave itself was ahead of it's time. i was using it very much.