• Otter@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    There’s a quote along the lines of “User error is not a thing, the system allowed for the error through bad design”

    Which can be true depending on how far you stretch it. I’d say that if a chunk of the user base is having a problem, it’s a design problem

    • dfyx@lemmy.helios42.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 year ago

      I recently had a case at work where you could move an object by holding the left mouse button and delete it with the right mouse button. If you deleted it while moving, you got an error message and the program would crash. It was an easy fix but afterwards I had a one hour discussion with our usability engineers if what I had fixed was a bug (my opinion) or a user error (theirs).

      • Jesus_666@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        That one’s easy. Is the crash part of the program’s design?

        If not: It’s an implementation bug, the program is not behaving as intended.

        If yes: It’s a design bug, crashes shouldn’t be intended behavior.

        • dfyx@lemmy.helios42.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Their argument was along the lines of “The requirements and design don’t specify what should happen if you move and delete at the same time so it can’t be a bug. Behavior that doesn’t violate the design but also doesn’t lead to the result the user wanted is a user error”. My argument was that we can’t always specify the interaction between arbitrary features other than “If the user does two things at once, at least one of them should be executed, ideally both” and “the program shouldn’t crash just because the user did something unexpected”. Otherwise our design document would be ten times as long.

          • Jesus_666@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            1 year ago

            Yeah, that’s basically the kind of logic you use when designing a low-level programming language: If we didn’t define what happens here then anything that happens is correct behavior and it’s up to the user to avoid it.

            Of course applying that logic to a GUI application intended for a comparatively nontechnical audience is utter madness.

            • mobotsar@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              That’s the kind of logic people historically used when designing low level programming languages. It’s not the kind of logic you should use or that people nowadays usually do use. Undefined behavior is widely seen as a Bad Thing in the programming language design community.

              • Jesus_666@lemmy.world
                link
                fedilink
                arrow-up
                0
                ·
                1 year ago

                Oh, don’t get me wrong, I fully agree. Undefined behavior is terrible UX and a huge security risk.

                Undefined behavior was kind of okay when RAM and storage were measured in kilobytes and adding checks for this stuff was noticeably expensive. That time has passed, though, and modern developers have no business thinking like that, even ones working on low-level languages.

                I should’ve phrased my comment differently.

          • nous@programming.dev
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            Hey, the design specs never said the program shouldn’t blast out and air raid siren at full volumn every time the user clicks a button. Cannot be a bug, must be user error.

            • dfyx@lemmy.helios42.de
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              You would think so, right? But that doesn’t have a requirement ID so apparently it can’t be referenced in the incident report.

                • dfyx@lemmy.helios42.de
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  1 year ago

                  Software for a medical device. Everything needs to be done exactly right and documented in three different places or else the regulatory agencies from at least three countries get really angry at you and worst case pull your device from circulation. Less cowardice and more cover your ass. Still annoying though.

    • Kache@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      But IMO that’s one reason weird UX/design is not uncommon and can persist in dev ecosystems. The intended users are more proficient than average and most are able to work around most issues.

  • gadfly1999@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    But it is a skill issue, just II/UX design skill. Not software development skill.

  • tauren@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    You can’t “skill issue” yourself out from every situation

    If you can’t do that - that’s a skill issue tbh.

  • LeninOnAPrayer@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    This sadly excludes the majority of bad UX decisions that are done entirely to maximize users time inside of the app as well as display advertising.

    So many functional apps are destroyed by these incentives. There is literally a “skill issue” but in the opposite direction. The design is either purposely malicious in a subtle way with “dark patterns” (something Amazon is insanely guilty of. Literally just go try and return and item.) or is purposely annoying trying to ensure the user purchases the “free trial” to actually make the app functional. Knowing a lot of users will be charged at least once for the free trial.

    I guess my point is that there is so so so so much wrong with UX design today. But for the majority of people that’s not because of a bad programmer with no design knowledge. It’s on purpose in most cases.

  • kittenzrulz123@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Users: I demand OSS devs and Maintainers do X

    OSS Devs/Maintainers: Are you willing to contribute code or at least donate any money?

    Users: Uhh its OSS, you should just do all the work for free with no funding. Also I demand that your software be as polished and complete as (premium proprietary software) I demand you do X, I demand you do Y, because im entitled to free software.

    • MonkeMischief@lemmy.today
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I am sympathetic but also so damn tired of seeing what essentially translates to:

      “Look, [megacorpo] bought out my school’s ecosystem so that’s all I learned. It’s “industry standard”, I can’t believe this FOSS can’t even do this one niche corporate-job feature, therefore it’s objectively terrible / not ready / inferior / useless for job work.”

      Which can usually be further boiled down to:

      “I tried it but it wasn’t a carbon copy of my preferred corpo-ware without any strings attached so it basically sucks.”

      • Bimfred@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Counterpoint: Blender was the first 3d modeling tool I tried and I bounced off that UX so hard that I haven’t touched it in nearly 20 years. Sometimes a bad UX is just bad UX.

        • MonkeMischief@lemmy.today
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Sometimes a bad UX is just bad UX.

          Totally can be! Absolutely!

          Although Blender’s amazingly usable now and has had lots of love in that regard! But it took a LOT of support to get this far.

          Good UX is crazy important.

          I think I’m more irritated at the people who seem to show up in so many FOSS discussions, expect FOSS alternatives to compete 1:1 with their billion-dollar corpo-ware of choice, demand the world of it, offer zero support, and then declare “it sucks and isn’t ready for the real world” because it’s not so perfect that Autodesk and Adobe are like “Well we’ve had a good run, guys.” and give up lol.

          I sympathize because I know where the frustration comes from. They’re sick of their tools being held hostage by interests that constantly seek to screw them! But change requires flexibility, cooperation, and support.

          I think a lot of people just don’t want to say “I want Maya/Photoshop/Excel/Solidworks/Windows/etc…but free and without dark-patterns!” (Don’t we all lol) Because they know that sounds unreasonable (yarr aside lol) , but people tend to get settled and comfortable with whatever got to them first.

          But taking that out on the community isn’t helping anybody.

          Constructive criticism of UI/UX is absolutely essential though, and requires a lot more understanding of how humans interact with things than simply “Well, billion-dollar-ware has always done it this way.” Haha

          • kittenzrulz123@lemmy.blahaj.zone
            link
            fedilink
            arrow-up
            0
            ·
            1 year ago

            Absolutely this, you cannot expect Blender level UI/UX without blender level funding. The fundamental problem is that new users/inexperienced users/nontechnical users arent used to contributing bug reports or even proper constructive criticism.

            Furthermore what people forget is that being a 1:1 carbon copy of a corporate software isnt inherently a good thing. For example Linux, I love Linux and I love the way it works. I use it not because its OSS but because I genuenly prefer it above Windows, I dont want Linux to be like Windows. I love tiling, I love Sway, I love Hyprland, and despite being in alpha I love the Cosmic Desktop. I dont care that tiling isnt immediately intuitive to Windows users, I absolutely love it.

            While im at it I absolutely despise the idea that the Terminal is inherently not user friendly (especially with a shell like fish). The idea that just because somebody isnt used to something makes it bad. Or that having to use a wiki/look at the docs means its “not ready”. All software is new to somebody at some point, that doesn’t make it bad.

  • Omega@discuss.online
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I like GTK and it’s really simple to make good looking functional UI with GTK4, but apparently people have a hate boner for anything good looking, GTK or Gnome related

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      GTK is the better looking girl at the sock hop. QT’s dress is a little ratty and she’s still got that lazy eye.

      QT has a certain “Ah that’s good enough for now, I’ll fix it later” feel to it, while GTK makes things that look done. It’s such a shame they wasted all that potential making something as rectal puke as Gnome out of it.

    • arudesalad@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      From what I’ve heard about it, it’s because the default gtk style only fits in with gnome, and gtk4 made it really difficult to customise it and is also really buggy on anything not gnome.

      That’s what I’ve heard anyway, I’m not a distro dev and the distro I last used is still on gtk3

      • azertyfun@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Nowadays “buggy” is not how I’d describe it, though there were certainly teething issues at the beginning. By now other DEs have learned to deal with it.

        However it’s still true that the GTK4 design is ill-fitting, and very opinionated. Quite exemplary of this are the applications that hardcode the GTK file picker (like Firefox and chrome) even though it’s inferior in every way to the Qt file picker and forces the infuriating GTK “design” choice of doing fuzzy search when you type in the file list instead of jumping to the relevant file. Very annoying when dealing with organized directories especially when no other file browser on my system works that way!

        • DaforLynx@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Thank you!!!

          I’m so glad someone else hates when applications hardcode the file picker, especially to the GTK one. I always have to remember it’s single click to open…

  • Shanmugha@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Point not made. First time around I read this as “elitist devs looking down on other devs thinking the latter can’t figure out a good UX”, which instantly gets countered with “it is a skill issue alright, but with all the people who design to UX to be exactly that (looking at you too, Android)”

    Ok, so this is about devs making software on their own and producing bad UX? Wow, news flash: most devs, even good ones, are not good UI/UX designers, that’s a completely different skill

  • ‮redirtSdeR@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    people always mention blender when talking about good ux in open source software, but i feel like the godot game engine doesn’t get enough love. it’s miles above of unity in terms of intuitiveness for me personally. plus it’s entirely customisable since it’s built in godot itself.

    • MonkeMischief@lemmy.today
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Godot is something I can still be super newb at and yet straight up admire. The nodes tree / scene system is a work of genius and I love it so much.

      I do feel like a lot of inspector bits suffer from unintuitive “hard to distinguish menu to sub-sub-sub-sub menu” UX, but I think the editor’s “expand all inspector headings” (or something) option is really handy for knowing what you’re working with, and mitigates that a little.

    • Flipper@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Remember when selecting something was done with the right mouse button in blender. That was great UX for beginners.

    • Flamekebab@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I thought it was just me! I’ve been using Inkscape for a long time now and I always feel I’m wrestling with the damn thing. I understand the principles behind vectors but I’ll be damned if I can consistently achieve what I’m attempting to accomplish.

        • dfyx@lemmy.helios42.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          OpenSCAD has pretty nice UX (though massively outdated UI look & feel) but of course describing your part in code is a very different use case from most other CAD tools.

        • ThePyroPython@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Counter point: KiCAD

          Yes I know it’s schematic capture and PCB layout, but I’m giving it as an example for two reasons:

          1. The UX is genuinely really good and easy to use even for a novice following YouTube tutorials because it follows the norms of a schematic/PCB software package you’d expect to pay for (OrCAD, Altium, etc.)

          2. It’s open source and used in industry so GIMP and Inkscape have ZERO excuses for their horrific UX which is the prime reason industry professionals don’t want to spend an age re-learning all of their workflows.

          There I said it, I’ll get down off this soapbox now.