• CherryLips@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 days ago

    Was a designer. You would be surprised how many times people want something how they want it. You can tell them that it does not make sense/is not visually presented information/is simply not designed…they just want to tell you how they want it and your job is to execute it. They also tend to love it afterwards. They usually believe they know better or are so focused on admin/following a line they can’t see sense…or nonsense in this case.

    • 0x0@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      10 days ago

      Reminds me of the time that a customer wanted square boxes and checkmarks in a web form, but only one was supposed to be selectable. I was like, this already exists — it’s called radio buttons. But they just had to be checkboxes for some reason.

      • Schmoo@slrpnk.net
        link
        fedilink
        arrow-up
        3
        ·
        10 days ago

        Then you just use radio buttons under the hood and override the appearance with CSS.

        • 0x0@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          3
          ·
          10 days ago

          This was circa 2010, and we didn’t have CSS appearance property yet. It wasn’t that much work, but I’d say it was non-trivial and I found it super annoying that I was going out of my way to make a UI that doesn’t work the way users expect.

          • Schmoo@slrpnk.net
            link
            fedilink
            arrow-up
            2
            ·
            9 days ago

            In my experience half of frontend development is bending over backwards to make everything look and work exactly like the boss/client wants even when you know what they want sucks for users, so I feel you.