This was actually not the conclusion I was expecting: > Don't bother improving your product unless it results in visible changes the user can see, find, and hopefully appreciate. I couldn't disagree more strongly. I can't think of the last time I encountered a UX change I thought was actually worth it. They're always bothersome, because now I notice the tool --it's no longer an extension of my mind and body, instead…
> I can't think of the last time I encountered a UX change I thought was actually worth it I mean, I am terribly glad we're done with Windows 95 and Android 4 style UX; aren't you?
If You Don't Change the UI, Nobody Notices (2009)
41–50 of 84 posts
Re: If You Don't Change the UI, Nobody Notices (2009)
#42Earlier quoted context omitted.
To be honest I think mostly nothing has substantially changed. Windows 95 isn't substantially different from Mac OSX 14 or Gnome or whatever. They're all the same clunky pointy clicky distracting paradigm where you have to memorize a bunch of visual rituals. The problem is that they change not which changes are "better" or "worse". By contrast, emacs has improved dramatically from v26, to v27, 28, and now 29. It's go…
I use and love emacs, but pointing to it as an example of how to evolve UX over time is indicative of your perspective. iOS/Windows/Android are used by the majority of people on the planet, emacs is not. Which UX do you think young people today and in the future will most understand? iOS/Android or emacs? Why is that?
Re: If You Don't Change the UI, Nobody Notices (2009)
#43There’s a flip side to this. If you change the UI for no reason, people get upset. For example, the latest iOS update flipped the speaker and mute buttons during a call. Why? No improvement was made, it’s just frustrating.
I'd go a step further: if you change the UI for no functional reason, you are a bad person who is causing needless consternation, confusion, and productivity loss. Even if you believe you have a functional reason, you had better think really long and hard about whether the supposed improvement you want is worth the pain of every single user needing to adapt to that change.
Re: If You Don't Change the UI, Nobody Notices (2009)
#44Earlier quoted context omitted.
To be honest I think mostly nothing has substantially changed. Windows 95 isn't substantially different from Mac OSX 14 or Gnome or whatever. They're all the same clunky pointy clicky distracting paradigm where you have to memorize a bunch of visual rituals. The problem is that they change not which changes are "better" or "worse". By contrast, emacs has improved dramatically from v26, to v27, 28, and now 29. It's go…
I use and love emacs, but pointing to it as an example of how to evolve UX over time is indicative of your perspective. iOS/Windows/Android are used by the majority of people on the planet, emacs is not. Which UX do you think young people today and in the future will most understand? iOS/Android or emacs? Why is that?
Re: If You Don't Change the UI, Nobody Notices (2009)
#45This was actually not the conclusion I was expecting: > Don't bother improving your product unless it results in visible changes the user can see, find, and hopefully appreciate. I couldn't disagree more strongly. I can't think of the last time I encountered a UX change I thought was actually worth it. They're always bothersome, because now I notice the tool --it's no longer an extension of my mind and body, instead…
I just wanted to say I agree and I was thinking this would be the conclusion as well. I cannot count how many times a major versioning of a large piece of software that was tied in with a UI redesign signaled a massive overturning in positive usability and focus of the authoring company but.... it's been almost every time. The greatest 'power user' focused engineering programs I formed my career around all had someth…
> the MBA's and 'Designers' doing the rocking are under the impression they are smarter than the people who built the boat in the first place.
Exactly. It's a function of power and incentives. In the organizations we build there are people who have the power to hurt users, and the incentive to exercise that power in a visible way. They aren't intending to hurt users, that's just a by-product. Instead, they're trying to "delight" users, as if the user is some kind of infantile homunculus instead of a thinking person doing important work.
Re: If You Don't Change the UI, Nobody Notices (2009)
#46There’s a flip side to this. If you change the UI for no reason, people get upset. For example, the latest iOS update flipped the speaker and mute buttons during a call. Why? No improvement was made, it’s just frustrating.
> If you change the UI for no reason... This appears to be not true for the OS (but only for Apps / websites). I'd say, for personal devices, folks expect a shiny new UI every OS update. For ex: iOS and Android are always in contention for who changes UI the most, from one version to another. Besides, styling changes and form changes are not the same.
Re: If You Don't Change the UI, Nobody Notices (2009)
#47Notepad has had some surprising improvements. I've not used it in so long that when I did open it and saw it had tabs, and recover unsaved documents, and dark mode, I wasn't sure it was notepad.
I remember when Ctrl+S in notepad didn't save, that one took a surprisingly long time to arrive.
However I remember hitting Ctrl+G to save often
Re: If You Don't Change the UI, Nobody Notices (2009)
#48This was actually not the conclusion I was expecting: > Don't bother improving your product unless it results in visible changes the user can see, find, and hopefully appreciate. I couldn't disagree more strongly. I can't think of the last time I encountered a UX change I thought was actually worth it. They're always bothersome, because now I notice the tool --it's no longer an extension of my mind and body, instead…
What if it improves your experience with the tool? For example, the page that annoyed you because it would load 3 seconds now loads instantly? This could be even not because of some flawed initial design, but due to unrelated technology advancements that are available just now.
Re: If You Don't Change the UI, Nobody Notices (2009)
#49Earlier quoted context omitted.
I use and love emacs, but pointing to it as an example of how to evolve UX over time is indicative of your perspective. iOS/Windows/Android are used by the majority of people on the planet, emacs is not. Which UX do you think young people today and in the future will most understand? iOS/Android or emacs? Why is that?
It depends what these people are using a computer for. If they're writing software, then a shell, a text editor, and a language toolchain are what they'll be using. Bash/zsh/fish, emacs/vi(m)/whatever, gcc/llvm/cargo/babel/etc. These are all tools with UX. But these tools--the ones programmers use--don't change willy-nilly. Doing so would hurt us , so we don't do it. Why do we treat "non-technical" users differently?
You think tools that stagnate will continue to see the same levels of adoption in new generations of programmers? It's an empirical question, I guess I just don't see it, and I say that as someone who loves vim & emacs.
Re: If You Don't Change the UI, Nobody Notices (2009)
#50Earlier quoted context omitted.
I use and love emacs, but pointing to it as an example of how to evolve UX over time is indicative of your perspective. iOS/Windows/Android are used by the majority of people on the planet, emacs is not. Which UX do you think young people today and in the future will most understand? iOS/Android or emacs? Why is that?
Familiarity