For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off.
For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off.
The root cause is that UX folks almost never use a product as often as their users.
So what's an "oh, left instead of right" minor change for them is anathema to someone with muscle memory.
Ergo, IMHO, all breaking UX changes should be required to clear a high bar, with the default being status quo + tweaks.
- We now have a plethora of UX logging and can see real time where users struggle.
- There are dedicated UX teams whose sole focus is to improve UX.
- More people are using technology than ever, and so we have a more representative sample of data to work with.
But despite this, UIs have consistently gotten worse over the past 10-20 years. I think there are a few possible culrpits. - Mimicking mobile UIs, as eloquently called out here: https://news.ycombinator.com/item?id=45290812
- I suspect there is something of a race to the bottom WRT To UX teams; they're always designing around any pain point, which has a few knock-on effects:
- There will _always_ be pain points, and so there will _always_ need to be UI changes.
- Designing a product so that the bottom of the bell curve can use it well probably does make an objectively worse product.
- There's nothing wrong with needing to learn a UI, and this "learning" could be mistaken as pain point.
- UX teams can't exist if there aren't things to constantly change, which increases the UI churn.
In concert, you have a UX which is constantly changing, and never really getting better, and often getting worse.Imho, this is a big source of the problem.
Granted: there are some amazing UX designers and teams out there.
But my experience with UX teams has been that in most middle-market companies they're usually less that sort and more the {huge designer ego} + {management consulting political skillset} one.
And it's a tough problem to solve! Because ultimately you want someone who can argue very hard for their approach to improving UX (usually against opposition from others). But when someone's ego exceeds their skill, that leads to disaster.
And without a strong Jobs-esque "this sucks" arbiter over them, their changes make it to prod.
Mature products need the maintainer mindset a lot more than the builder mindset.
It's hard enough to find devs who are good at maintainer-mode. I think it's even harder with other roles.