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.

https://mastodon.social/@tuomas_h/114672109542813969

  • Zorque@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 months ago

    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.

    • brandon@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      7 months ago

      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.

      • Paul in de Emiraten@mastodon.nl
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        7 months ago

        @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.

    • parody@lemmings.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      7 months ago

      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… :)