It's not like I just change things for the sake of change
It's not like I just change things for the sake of change
How dare I polish and remove kludges from previous releases. 😆
Also, none of those kludges would have even been necessary if the project scope was properly defined from the start and the project manager didn't let the users keep trickling in new requirements without also extending the deadline.
So yeah, how dare I go back and implement something the way it should have been done the first time?
There's always a relevant xkcd. Lol
This is such a masterpiece from xkcd
I still can't do half the stuff in the windows settings app that I could in the control panel, and every update removes an option in control panel without an adequate replacement.
Inb4 "use Linux" I DO but Nvidia and Wayland is still BORKED (even with v555) and when I'm done with work I just want to load up a game and not have to fuck with drivers and never actually play. Sue me.
I'm 100% linux, even on my work PC, but I will spare you the evangelism. lol
It's pretty safe to look at Microsoft as a shining beacon of what not to do when it comes to (re) design. I'm not an Apple fan, but I do respect that OSX has basically just had incremental / evolutional UI changes since it was first released. Any major differences (AFAIK, anyway) were slowly and progressively implemented over several versions.
What's wrong with X11?
About a year ago I tried switching to Linux and used Linux Mint exclusively for about a month and a half.
I have multiple monitors with different refresh rates, one 144hz and a 60hz monitor. The problem is that the compositor runs at the lower of the two, for both monitors. In theory it should be possible for a full screen app like a game to bypass the compositor completely, but I could never get that to actually work, games running in both exclusive full screen and borderless were kneecapped to 60hz video output because I had the audacity to use a secondary monitor connected. But even if that did work correctly, regular desktop use would still be kneecapped. Admittedly not as important, but still annoying. I ended up having to use a hacky config tweak to force the compositor to run at 144hz, which worked but also caused tearing on my secondary monitor.
On top of that, X11 straight up does not support VRR / G-sync if you have more than one monitor. And HDR? Completely unsupported.
Same boat brother ... don't let the hivemind bother you. I deal with an oracle linix at work for 8h a day, when I get home I don't want to spend time fixing my own shit ... even if it's going to be better in the long run.
I'll switch to Mint the second ricochet anti cheat has native proton support ....
Nvidia and Wayland is still BORKED
Nope
Nice try Microsoft, I still don't like your monthly "small" ui changes that hide the features I use and add extra "get copilot now" buttons
They even put a "Github CoPilot" button to Visual Studio FFS. Fortunately they at least added an option in the config, which unlike most UI elements in VS requires a restart. But at least it can be removed I guess.
Didn't think MS would enshittify VS because "Developers! Developers! Developers!" but here we are.
This is what I imagine the Reddit developers think of themselves as. 😆
Ouch! 😆
Yeah, I'm sure that almost all of us have felt this way at one time or another. But the thing is, every team behind every moronic, bone-headed interface "update" that you've ever hated also sees themselves in the programmer's position in this meme.
Oh for sure.
The meme is just a very exaggerated tale of moving a tacked-on, added-at-the-absolute-last second button from the previous release into the action menu where it should have gone originally. It's an in-house application, and the people that complained are also the type that will bold an entire page because "it's important". lol
In all my life I've only experienced one UI overhaul that I considered an improvement, and even then there were a few specific features that were a step backwards, even by proper design standards (the same action did two different things in only slightly different scenarios.)
Buuiuuuut I know half the time it's just because I'm used to the old way, only the other half is it some corporate bullshit trying to push a feature no one asked for.
Yeah, I get that completely. Which is why I rarely, if ever, overhaul the whole interface.
Pretty much every change is a refinement rather than a complete redesign. In this case, the complaint was because I moved a button that was just kind of tacked-on last minute in a previous release into the action menu where it should have gone to start with. lol
I can't believe you moved a button. HOW COULD YOU??? I trusted you, Patrick.
So. How long have you worked for Google? Not in years; in chat apps.
What's the difference?
A year lasts longer
Yeah, what you have to remember is that most users are pretty dumb. They don't know how the software works, just where the buttons are to do the thing they want to do. They don't read anything or learn anything other than what is needed for some menial task, and that they're only employed because the company they work for is too small for it to be automated.
If your stuff is free then do what you want, but the second you start charging money for stuff, you have to be acutely aware that the change that makes sense and makes everything neater and cleaner is going to make some 65 year old in an office freak the fuck out because now they can't do their job because their buttons have moved or the icon has changed.
Automating menial tasks is literally what computers are for.
Hrm, I would argue that if your update gets in the way of productivity on the user side, then it's actually worse, not better.
Sure, in a vacuum it might be superior, but that is now what is happening.
We used to rail against our users always wanting an Excel like view for everything, but when you observe them working to understand their work flow it makes sense. They use excel the other 75%of the day, we're the one breaking their mental flow and ruining their productivity.
Just because someone got used to walking around on their knuckles doesn't mean walking upright isn't easier and better overall. Sure, it will be difficult, it will be uncomfortable, and they'll have to get used to it before they see any improvement, but once they get past those hurdles even they will be amazed at how fast walking upright can be. And in the meantime, no one else who already has a tendency to walk upright will have to go through the pain and inefficiency of walking on their knuckles.
Some people don't have time to learn new workflows at their job. Their workload is maxed out with the workflow they currently have and while their boss may understand they need time to learn a new workflow, the bean counters up the chain won't. Maybe their replacements will get trained on the changes you made but the current ones are fucked.
And that's why you don't have a 6 month sprint...
Yeah holy shit! I hope this is a made up example. A six month sprint where you change literally everything about your UI? No wonder customers are upset!
I've previously worked at a company that did that lol, but they had a toggle to turn it back to the old UI, and everyone kept switching back to using the old UI, including new customers.
To be fair the old UI was looking really dated, and needed a refresh, but it was functional and didn't really need a complete overhaul, should've just updated the style.
Not if the new UI consists of a single
closebutton: "make whatever I want"
The trouble is that, apparently, "perfect UI" can mean "let's take all the sidebar tabs, remove their text labels and make all their icons really abstract and in the same colour. Oh, and change their order, too, while you're at it."
Thank you from the bottom of my muscle memory and pattern recognition. Now, give us back our old UI that was actually meaningful, or at least make it an option if you insist that your "clean look" is more important than actual usability.
^(Apart from that, I love you JetBrains.)
the user is always right
Yep, lol.
- The user is always right
- The user has no fucking clue what they want
I hate how both of those things are true at the same time 😆
It isn’t always that they don’t know what they want, sometimes they just don’t know how to describe what they want, or they may know what they don’t want.
This may shock and amaze you but...
there is more than one user for your product. If you don't know that, it sounds like you either haven't done a user survey or you haven't created the correct user profiles (based on that survey).
Creating a "perfect UI" without asking users what they want is not good UX. It's just masturbation. The user survey tells you that people want A B C, etc. and in which order. You should know exactly how your changes are going to be received when you release them.
Imagine a restaurant that doesn't ask you what you want. Instead the chef tells you "This is the best food possible" and just makes what they want. That's what developing without a user survey is like.
The user is always right about what they are willing to spend money on. That doesn't mean they know what they want, although a lot of people don't want to change.
That doesn't mean all change is good, and it isn't like any UI will ever meet everyone's preferences. For example, I hate adaptive design interfaces that are significantly different in confusing ways on different resolutions. Like I understand switching a static menu to an expandable menu, but not moving the relative location of certain buttons from the bottom of the screen to the top or vise versa. But that might make sense for some use case that isn't how I interact with it.
The user will forget about the old UI after 2 weeks.
I still constantly bitch about not being able to pin the taskbar to the side of the screen in windows 11.
There will always be some static-friction to UI changes, even if it's a change that makes the UI more accessible overall. Everytime you alter your UI you're taxing your users as it will take them some time to adapt to the new system. You should minimize how often you do this for that reason. Additionally, sometimes you may be unaware of an unintentional feature users appreciate that you're depreciating.
I dislike your comment because it's making a lot of sweeping generalizations (like that the UI changes are actually good) and ignoring the fact that users may have legitimate complaints.
Exactly. When discord updated their mobile UI everyone immediately hated it cuz different. There were legitimately some poor decisions made, but then they went and reverted like half of it after people had started to get used to it. For example, I got used to and liked where they moved dms to and they reverted it back, but kept having to tap on the name of a channel to view the users in it instead of just swiping left.
Edit: and I'm also now used to the bad things they kept.
If this were true we would still be riding horses.
That's a stupid bug report!
For once, a username really checks out.
😆
Sometimes this is true, but sometimes UI updates really are just bad. Euro Truck Simulator 2 redid its UI in 1.50 and it's so much harder to use. Everything used to just be convenient buttons and information on the main menu, now everything is in really confusing menus and even though it's been out for a few months now I still have so much trouble using it and it feels so good to go back to an older version with a good UI. (Also the new UI is just horrendously ugly because they made everything completely flat but that's just personal taste I guess)
🏅
There is a dangerously large population of devs and managers that look at themselves, unironically, as the gigachads pumping out ui "upgrades"
Many of these fail to realize how disruptive it is. UI change is like API breakage for the brain.
I have lost track of how many times I've tried to help an elderly family member with an app after some pointless, trivial, ui change. Only ending with them entirely giving up on using the app after the "upgrade" because the cognitive overhead of the change is beyond the skill that can fairly be expected for them 💔