Apple love to preach “the UI gets out of the way of your content” with each new redesign, but how true is that in practice? Let’s compare the total height of the Safari UI with a toolbar, favourites bar and tab bar visible, across the three latest Mac OS design languages – Yosemite, Big Sur and now Tahoe. I’ve added a red line for emphasis.
It sure looks to me like the UI is eating more into my content with each redesign.
Even if people had dual 36" monitors or whatever, most sites or programs seem to focus more and more on making things fit into as small a horizontal space as possible. Even if you have a vertical mo it or you’d have huge swatches of white space along the edges of the screen.
For horizontal space, it tends to be really hard to design for larger widths and still maintain focus on the main content in a readable way. For example, you should avoid super wide blocks of text as it’s really easy to get lost as you read. This is why you often see a max width with large gutters for wide displays, especially on pages with a singular focus, such as an article.
Do people really have that much trouble focusing as they read? Honestly I have trouble focusing when you fit maybe a dozen words per line, with giant swatches of nothing surrounding it. I have to change any wiki article I read to the wide format or it’s virtually unreadable to me.
Very much so. The longer the line, the more your eyes move and the easier it is to lose track of where you are. It can be worse when you move to the next line, as you lose your frame of reference from the previous line on the other side of the screen.
@brandon @Zorque This has been researched about hundred times and for most readers in the Roman alphabet lines between 55 and 70 characters - a space is a character too - are easiest to read. Hence scientific articles in Latex and similar later text mark up languages use two columns on a A4 paper.
So why dont sites use multiple columns?
That is funny! I’ve opted-in to change the default & tried the wide format on Wikipedia a few times and each time it has reinforced what I perceived to be the obvious developer decision based on (ostensibly) the “obvious“ user preference… :)
That you’re terrible at reading?