Slashdot Mirror
Ask Slashdot: Should Open-Source Developer Teams Hire Professional UI/UX Designers?
OpenSourceAllTheWay writes: There are many fantastic open-source tools out there for everything from scanning documents to making interactive music to creating 3D assets for games. Many of these tools have an Achilles heel though -- while the code quality is great and the tool is fully functional, the user interface (UI) and user experience (UX) are typically significantly inferior to what you get in competing commercial tools. In an nutshell, with open source, the code is great, the tool is free, there is no DRM/activation/telemetry bullshit involved in using the tool, but you very often get a weak UI/UX with the tool that -- unfortunately -- ultimately makes the tool far less of a joy to use daily than should be the case. A prime example would be the FOSS 3D tool Blender, which is great technically, but ultimately flops on its face because of a poorly designed UI that is a decade behind commercial 3D software. So here is the question: should open-source developer teams for larger FOSS projects include a professional UI/UX designer who does the UI for the project? There are many FOSS tools that would greatly benefit from a UI re-designed by a professional UI/UX designer.
I have a damn good answer for this. Because UX/UI cannot be handled by unit tests, and does not have a definite "better" or "worse" condition at face value. I cannot count the number of times I've proposed pull requests for UX issues in open-source projects, only to have them either massively argue about the need, or flat out reject the PR. One of the more recent ones, a router OS which has basic IPv6 support was displaying IPv6 delegated subnets wrong. As an end-user, this confused me and went against my knowledge of being a network admin. As a software engineer, I went in and check the UI code which displayed the info. It was a trivial bug to fix, but instead of fixing the bug, the project lead decided to take the entire feature out as a way to "fix" it. So, instead of display correct information or even wrong information, just display NO information at all to the end-user!
The two key areas where developers need to learn to open up more to contributions is for UX/UI, and for documentation. Recently I discovered that there is a dedicated group of technical writers in Seattle who are the equiv open-source software engineers, they give some of their spare time to help document open-source projects. They've been really nice, host workshops, and teach their trade openly. *THIS* is what we need in open-source, more disciplines besides just software engineers.