5 ms·
Meh. Any significant interface change is going to annoy some users. It's pretty unavoidable. Unless there are actual, real, usability issues or feature reductio
by kccqzy 6y ago
Meh. Any significant interface change is going to annoy some users. It's pretty unavoidable. Unless there are actual, real, usability issues or feature reductions in the new UI, what typically happens is that after a few weeks of complaining, most people just get used to it. If your product is important enough, you can even get away with some usability issues or feature cuts—users will use your product in spite of those feature cuts.
A recent UI redesign that wasn't very well received is Google's code search redesign. Compare, e.g. the same page on the old one[0] and the new one[1]. It looks jarring at first sight if you're used to the old one, but ultimately people just need to accept it and move on.
[0]: https://codesearch.chromium.org/chromium/src/third_party/blink/renderer/core/html/forms/html_input_element.h https://codesearch.chromium.org/chromium/src/third_party/bli...
[1]: https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/html/forms/html_input_element.h https://source.chromium.org/chromium/chromium/src/+/master:t...
- krackers 6y agoThe new code search takes a second to load each file. The old one does it instantly. The xref panel has almost zero contrast between the section headings and the filenames. Vertical space is wasted by a "cross references" bar that persists even when closed. For some reason the blame button is at the top but history is at the bottom. The "layers" are also missing in the new version.
- vijaybritto 6y agoYes, I just checked it. Its so fast in the old version. There is no loading spinner at all. The amount of js loaded is 661kb in the old vs 1.2Mb in the new :| Total resources(after decompression) for the site: Old -> 2.6MB (:thumbs_up:) New -> 8.5MB (:what:)
- fnordsensei 6y agoIt would be OK if the additional size actually bought you something, like speed. But it doesn’t, somehow the opposite is true.
- bertmuthalaly 6y ago> Any significant interface change is going to annoy some users. It's pretty unavoidable. I'm usually with you, but you could not have picked a worse example - adding (or removing) latency to the critical path of how we read and think about code has large downstream effects that are difficult to measure and difficult to get fired (or promoted) for.
- jrockway 6y agoAt some point, you do have to update the interface to move things forward. In the early days of programming, you had to manually punch cards. Then someone invented teletypes and you could program with ed. Then someone invented screens and you could use vi. No doubt each of these changes were incredibly jarring on the first day, but the change was worthwhile overall -- using a visual editor is much more productive than managing stacks of punched cards. If everyone took the approach of never making anything that would have to be learned, our field probably wouldn't even exist.
- TeMPOraL 6y agoThe examples you mentioned brought usability benefits. Teletypes were obviously better than punch cards. Screens were obviously better than teletypes. Even GUIs were obviously better than CLIs for a lot of applications - they've essentially opened up new domains of work on the computer. Here, we're talking about replacing perfectly good interface with one that's strictly inferior in terms of usability and features. Or, in the Google code search example, changing a few colors, and in the process significantly downgrading usability due to adding latency that wasn't present before. Change is good if it brings something better, or new, or opens up the road for further improvements. These changes discussed here are doing neither.
- jimmaswell 6y agoRedesigns should never, ever happen unless absolutely necessary. They're basically never worth it and almost always worse than before.
- jacobolus 6y agoIn particular, the people doing the redesign often seem to not understand what made the first design successful/effective, and senselessly wreck parts without even realizing. I’m not sure if this is because they understand the problem less than the original designers, the institutional incentives are set up poorly to encourage high quality work, increased system complexity / technical debt is harder to work around, institutional complexity makes it harder for competent people to be in position to make the decisions, the original successes were partly down to luck and reversion to the mean dooms follow-ups to mediocrity, recent UI fashions are generically user hostile, or what... but whatever it is, it’s very frustrating. And that’s not even mentioning the inevitable bugs and glitches. There’s probably some selection bias involved too. Those products and redesigns which are amazing and wonderful get used, but nobody thinks too hard about all the ways in which they are better. On the other hand when redesigns negatively affect customers, the bad experience is unpleasantly memorable.
- will_pseudonym 6y agoIt's like rewriting a codebase. There's so much tacit understanding of the actual problem inherent in a living design/codebase. All that nuance gets obliterated because someone got a bee in their bonnet about better code/cleaner design.
- deleted 6y ago[deleted]
- hbarka 6y agoAdd Google Finance to this list. What a tragedy and Google still has not realized it.
- IgniteTheSun 6y ago
- NikolaNovak 6y ago[FWIW, for me at least, your first link redirects eventually to same as latter, though I can then click "return to code search v1" to see what you mean ]
- TeMPOraL 6y ago> If your product is important enough, you can even get away with some usability issues or feature cuts—users will use your product in spite of those feature cuts. This is true for most software products these days; between network effects and alternatives being different enough to require relearning, users will bear a lot of annoyance before giving up. Users are sticky. But that's not a justification for doing changes for change's sake, making things worse from one iteration to another (hello, Google)! On the contrary! The vendor is in a privileged position in a relationship here, and should not abuse it. Making pointless redesigns, reducing functionality, dumbing software down, decreasing usability - those things are making the days of many people worse, in subtle and not so subtle ways. Software scales, and so its effects, including making people unhappy.
- thaumasiotes 6y ago> between network effects and alternatives being different enough to require relearning, users will bear a lot of annoyance before giving up. Users are sticky. It's been pointed out elsewhere, but the flip side of network effects is that if you do push your users into leaving, they all leave at once. That can be hard to deal with.
- acituan 6y ago> Meh. Any significant interface change is going to annoy some users Your example is unfortunately worse than just interface change. It is also worse than just usability degradation. It is about why and how this change could take place to begin with. For the case of chromium, I think this is just change for change's sake, so that some team can get promoted, some director can justify their existence. I wouldn't blame the team for wanting to get promoted, but I would blame the process that allocated world class engineers and designers to a task that was not only redundant but also ended up being a net negative to its users. This was a process that obviously couldn't integrate user feedback, that couldn't decide "you know what, let's not release this until these issues are addressed" probably because it "had" to be released at that arbitrary deadline. This is like paperclip maximizer, only it is not artificial intelligence but corporate intelligence destroying the world one useless launch at a time.
- IgniteTheSun 6y agoI've also seen many a perfectly functional website redesigned and changed because it was thought to be too reminiscent of the 1990s web. I use PubMed a lot - in the case of this redesign, I don't see any real advantages to the redesign but I see a lot to dislike. I'm sure web designers strongly prefer the new design but actual users like me strongly prefer the old design. People trying to make money on redesigning sites sell the supposed need to look modern and site owners seem to always fall for it leaving users to pay the price in terms of lost readability and usability.
- iagovar 6y agoPubMed users are experts, not your average dumb user. Experts need information, not a thousend clicks and lose time in the interface. In short, they need help not to fight your website.
- rpedela 6y agoPubmed has needed an upgrade for at least 15 years. The fact you could search for the exact article title in the old version and never find it says a lot.
- IgniteTheSun 6y ago"The fact you could search for the exact article title in the old version and never find it says a lot." This implies the need for server-level improvements, not changes to the user interface.
- rpedela 6y agoFor that specific example, they needed both. You could craft a custom query to accomplish that every time in the old version, but you really needed to know what you were doing. Now that they changed some defaults in the UI and made search improvements on the back end, I haven't seen that specific problem since.
- gurkendoktor 6y agoAt the extremes, we know that people will even happily accept regular crashes[1]. That doesn't mean users should just accept everything without complaining (which is what your comment seems to imply). https://9to5google.com/2016/01/04/facebook-intentionally-made-its-android-app-crash-to-test-how-addicted-users-are/ https://9to5google.com/2016/01/04/facebook-intentionally-mad...
- arexxbifs 6y agoWith any UI redesign, you have to ask yourself: is it better or is it just different? If it's better, the improvements should be easy to point out and any changes introduced should have clear motivations. Prettier isn't really a factor here: UI:s can usually be made prettier (which usually just means "reflecting current design trends") while still retaining their functionality (even if it requires a complete rewrite behind the scenes).
- TeMPOraL 6y agoIronically, in case of the Google code search, all they needed to achieve the new aesthetics was a bit of CSS. I can't find any reason to justify the degraded functionality.
- IgniteTheSun 6y ago'''UI:s can usually be made prettier (which usually just means "reflecting current design trends") while still retaining their functionality (even if it requires a complete rewrite behind the scenes).''' Unfortunately, the one evaluating whether is looks prettier or is more usable often has career or financial goals driving the changes rather than users true interests. How many easily readable sites have changed to "prettier" fonts and light colored text on white backgrounds in the last 15 years?
- throwaway_pdp09 6y ago> If your product is important enough, you can even get away with some usability issues or feature cuts—users will use your product in spite of those feature cuts. Messing with your users because you can is not nice.
- zouhair 6y agoI tried to use the new Reddit UI and it is factually less useful than the old one. Two things that bother the most in changed UI, having less information in one screen (be it having to scroll to get the same information as the old UI or just less info than the old one) and adding useless clicks.
- disposekinetics 6y agoWhen I took a look at the new Reddit UI I was struck by how hard they are trying to replace browser features with in-app features. Most glaringly instead of using a browser tab, the expected behavior seems to be clicking into their modal for everything.
- globular-toast 6y agoI used to think this, but then I realised it is complete bullshit. It is absolutely possible to please users with a UI change. That happens when the old UI was broken. The only reason users complain about UI changes is when it was "fixed" but it wasn't broken. No users are complaining when actual problems and broken UIs are fixed.