>Why not instead of "change" just make a new interface and give users the option to switch if they want. This approach seems too rare.
Because it duplicates options, separates the users in two camps, adds 2 (or more if you keep doing it) interfaces for the dev team to keep supporting, and so on...
Re:Habits, UI changes, and OS stagnation
by 1vuio0pswjnm7 on Wednesday July 21, 2021 @06:44PM
(#27913111)
Give users the option to keep using the "familiar" interface, but without any "support". I suspect many user actually require "support" because of interface changes.
IME, observing other users, it is the forced change that is offensive to some. They do not complain about "lack of support" (many want to be self-suficient and do not want to keep asking for "support"), they complain about changes that they see as unnecessary and that will just require more effort to learn.
Re:Habits, UI changes, and OS stagnation
by orhmeh09 on Wednesday July 21, 2021 @07:11PM
(#27913331)
The UX staff have to do *something* while they’re employed. If their training is best suited to the development of brand-new products over maintaining established ones, and if they want to enjoy both job security and career advancement, the UI is in a constant state of flux. On the business side, I think there might be the belief that these updates could have some competitive or PR value.
Has anyone ever counted the number of times that Firefox has changed its UI. I would bet they have people working on a new one right now.
What do we call it when people keep "fixing" things that are not broken. When people misuse the word "broken" to signify their dislike for something.
If we dig down deep enough in the source code of things, I am sure we can some interfaces that do not change much.