They redesigned PubMed
sciencemag.org
sciencemag.org
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/bli...
[1]: https://source.chromium.org/chromium/chromium/src/+/master:t...
Total resources(after decompression) for the site:
Old -> 2.6MB (:thumbs_up:)
New -> 8.5MB (:what:)
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.
If everyone took the approach of never making anything that would have to be learned, our field probably wouldn't even exist.
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.
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.
Most computer interfaces can and should improve when the time is right.
The kind of redesign people are complaining about involves primarily changing how things look with neutral or negative impact on overall usability. People aren't complaining when suddenly you can do more with software, or do the same things but faster. They complain when features disappear, things slow down, or buttons get moved around the UI for no apparent reasons (that last one alone is enough to confuse the elderly and people without much patience for technology).
>Redesigns should never, ever happen unless absolutely necessary
There is a place for redesign, but it has to be done properly. It's not something intrinsically bad.
I generally agree with "no major rewrites" for both code and user interfaces. It's better to evolve, iterate.
There are two exceptions.
"Do overs", when you can start from scratch because of a new platform, plateau, biz model. While technically possible to iterate an architecture from sendmail (monolith) to postfix (collection of simple services), for example, it's easier (for a motivated expert) to just start over.
New metaphors. A new idea, paradigm, algorithm is so disruptive, you can just replace the prior solution. I once replaced a complicated CAD/Illustrator style production planner with a wizardy parametric designer. I once replaced a complicated BizTalk style "workflow" thing with a postfix inspired group of utilities.
Source: Recovering user interface designer, before the kids rebranded it "UX".
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.
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.
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.
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.
This implies the need for server-level improvements, not changes to the user interface.
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).
'''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?https://9to5google.com/2016/01/04/facebook-intentionally-mad...
Messing with your users because you can is not nice.
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.
These sorts of applications should cater to experts who use them daily vs. design standards du jour or new users, IMO. /rant
But sacrifices feature discovery and click fatigue in order to do achieve that goal.
ps: also how come they didn't roll out the thing in stages ? anybody in the medical field can tell if doctors or researchers were involved in testing a beta of this ?
On a personal note, I can still navigate the website as needed, but had to learn how to use the site again. Obviously, full functionality is still there, they just slapped a fancier skin on it with different formatting.
The original interface was excellent for the user community of experts.
It appears to have been designed by a third-rate UX designer for the average dummy, with no thought to what a professional user needs.
See: Dumbed down : https://pubmed.ncbi.nlm.nih.gov/
Original: https://pmlegacy.ncbi.nlm.nih.gov/
I cannot wait for these people to leave the industry and hopefully take their dogma with them. They’re the rebirth of the same mindset that led to the ‘eyeballs are all that matter’ era of the web in the early 90s.
Apple's design philosophy takes good parts of those three concepts and implements them well. Moving around essential functionality can be required in specific cases.
Maximalism can be just as poorly made.
For a bit of computer history, while it may sound quite far fetched nowadays, there were actually times when relaunches were generally welcomed and user numbers were expected to double rather than dropping. (Well, this was before UX.)
Edit: As an example, I suppose none of the much beloved and personality defining original Macintosh icons by Susan Kare could have come out of a modern UX work flow, nor the use of the Norwegian landmark sign as the marker of the command key. Or, where there any users that rejected the OS X Tiger and Snow Leopard UI, which applied quite radical changes to the previous Aqua UI?
Windows 95 gave you all kinds of stuff Windows 3.1 didn't have, Nintendo 64 vs SNES is another example.
Users want upgrades, not redesigns. If you give them a upgrade, no one cares about whitespace or rounded corners, that's why those things used to be an afterthought.
I know a few people who left Mac due to this change.
Win3.11 to Win95 springs to mind here.
In contrast, going from "good UX" to "better UX" is a whole different endeavor since you'll have to fight against the friction of people having to give up routines and flows that they have been sticking to for a long time. A thing which no amount of thoughtfulness and consideration of a redesign will be able to make up for – that is, initially.
For me this was the starting point.
After or around the same time someone from Gnome (or Red Hat?) realized (at least this is how I remember their marketing) humans think spatially - and used that observation to decide that everytime I click on a folder in Nautilus it should open in a new window. (Yes, it becomes a mess really quick.)
Also the insistence on removing every configuration option.
Same goes for Unity: my best explanation is someone heard Mac OS had great UX and decided to copy it wholesale: Move controls to the left. Change Alt-tab. Introduce dock.
Common for all these "improvements" is that nobody asked us users, and nobody cared to make it easy to go back.
I now have an acquired distrust of ux designers (and I am really happy whenever I meet good ones which thankfully happens often where I work.)
- Ribbon has mostly been fixed now, and is mostly pleasant to use even if the File menu is still jarring.
- Nautilus was fixed in the next major version.
- Unity was never fixed. I hear some people like it but I guess we are a good bunch of old Ubuntu users who cannot stand it. More importantly it is hard for me to see any reason besides arrogance for why there couldn't an option somewhere to get back to normal alt-tab.
The way I see it, arranging things in space works well when you have enough space to fit these things in; once you have to scroll or zoom, the utility rapidly degrades with the number of excess stuff. On top of that, remembering where things are works when there are couple things. Not when there might be couple thousand.
For comparison, it's worth thinking about two other things human beings seem to understand and employ rather well:
1) Lists. Note that while you may put different lists in different places, you generally don't generally put each item on a separate post-it placed in a different location. List items belong together.
2) Hierarchies. That one is probably biological, and almost as fundamental as understanding 3D space. We inherently grok hierarchies - both abstract and social. We navigate them every day.
Unlike spatial arrangement, hierarchies and lists scale well. And so that's why a filesystem is a hierarchy, and it's usually rendered as either list, or - if you need to see multiple hierarchy levels at the same time - as a tree.
I at least felt Gnome 3 was about the same only it was possible to configure it.
My plan was to use the Pop OS edition since they actually had put some thought into shortcuts.
Another DE I actually enjoyed despite being initially skeptic was Elementary OS.
After KDE 5 became stable though I've stuck with thatm
The designer and execs only look at new screenshots of the design, and ignore usability. Maybe a few minutes of thought and review are given to how a user interacts with the site, but only to talk through a narrow set of interactions that the designer took the time to bother with.
Site keep getting less functional (reddit, linkedin, yelp, twitter) and slower (everything google). All these companies encourage short-term thinking, and incentivize whatever looks good on a powerpoint or checks a box on their year-end goals.
Interesting observation. I've had this very situation with mobile apps, where users base their decision on whether to download an app largely on the basis of having a quick look at the screenshots. Adding the proper functionality and improving discoverability inevitably leads to a design which simply isn't as slick as the minimalist version. The only solution I can think of is to have an "advanced" version of the UI which users can enable.
This. (I have high hopes for Apple, now that J. Ive is gone.) However, mockup screenshots had always been the medium of communicating designs to the client. But the more prominent role of screenshots may further the concentration on just a few paths of usage, as we may observe it in the common reduction of interface options – which may be fine for the few selected usage paths and may provide the base for a "cleaner" design (which should actually be a design job, not a content issue), but necessarily fails a number of use cases.
Another point may be made about an overly application of metrics. The issue here is that all metrics that may be actually useful are in the qualitative domain, which is rather labor intensive, complex and expensive. (Especially the process of transforming qualitative data into quantitative metrics.) So everyone is going for quantitive data, which is cheap and supposedly easy. That only few of those involved have a background in social research and would actually know what they are doing, doesn't especially help. So we may add data driven design to the list of possible issues.
(Much of this may be understood in the old dichotomy of "art or engineering". While the engineering approach is fine for managing exchangeable labor, it's failing in many other aspects. Meaning, what you get is an exchangeable product and chances are that, if you actually have a unique product, this approach will fail your needs – or, at least, the needs of your customers.)
Then I tried Gnome and it was superlative in comparison. Honestly, maybe it was because we had nearly nothing. Everything was new and magical.
Now we start with a high baseline. Everything is already pretty good. A redesign rarely gives me more.
For a striking example, have a look at the hitherto excellent Norwegian weather site's short term forecast here https://www.yr.no/place/Portugal/Lisboa/Lisbon/hour_by_hour.... then click through to what they're humbly bragging about changing it to https://www.yr.no/en/forecast/graph/2-2267057/Portugal/Lisbo...
I can only assume neither the management nor the "design" consultant actually use the result. Oh, and consultant reminds me. Accountability is probably a major factor here. In my perception, the people causing this sort of destruction don't suffer any negative consequences of them. Maybe they even get promoted or get a prestigious client to list on their CV.
Looking at your weather site example, this is precisely the kind of stupid design decisions I so hate about modern software. On the old site, all the data is in one place, and can be read without any interactions. You can just glance at it and learn what you need (which also means you can do that while holding a toddler in one hand, and eating your sandwich with another). Who on Earth thought that dumbing down the table and forcing you to manually switch between it and the graph (and no option to show both!) was a good idea? What's up with information moved to graph tooltips? And where has the link to download the PDF version went?
Your point about accountability is probably spot-on. These changes aren't making the website completely unusable, just strictly worse and more annoying than before. That's nowhere near enough to cross the threshold after which anyone on the vendor side would care. That, multiplied by the number of users, it amounts to a lot of man-units of annoyance, doesn't even register.
The same thing happened with the recent SAO/NASA Astrophysics Data System redesign (https://ui.adsabs.harvard.edu/). Initially they planned to only have the very heavy SPA but after a few months of comments and complaints the team made a really excellent "basic HTML" fallback, https://ui.adsabs.harvard.edu/core .
No doubt PubMed will implement a similar full featured fallback to sane HTML if they want to remain relevant to researchers.
Good search, no JS required, loads fast, and looks modern for those who care. You can even export the results of a search to a CSV spreadsheet.
https://www.nlm.nih.gov/pubs/techbull/so09/so09_pm_redesign....
https://www.nlm.nih.gov/pubs/techbull/nd05/nd05_toolbar.html
Wow that is an intelligent insult, gonna start using that!
Now isn't this the deepest irony...
We've got ad-tech; you've got an opiate crisis.
No, come on. That's the imaginary world where everybody is in SF and works for startups or Google. There was a recent thread about enterprise software that discussed SAP and there were all these people who were like "what's THAT??"
It's like thinking of everything being made in China because all that you notice day-to-day is consumer products.
Edit: I thought about the word "plurality" some more, and technically, anything can be a plurality if you fragment all the other categories enough, I suppose.
Doctors were using free software that used dark patterns to get them to prescribe more painkillers, but the actual scandal was that the people making the software were getting kickbacks for it.
Sorry I don't have the link handy, but I probably read about it on HN.
This sounds interesting and I don't see a reference on google, have any links about it?
They do tech and know it, just a different kind.
For example, there was a whole range of technology encompassed in the transition from rubbing 2 sticks together to start a fire to pocket size lighters.
The terms "developing new technologies" can be heard in the seminars in fields having nothing to do with computers, programming, or the internet. One would need a good background in calculus, partial differential equations, etc. to understand many of the talks.
---- edit: typo - replaced "we" with "with"
I love the content on Internet Archive, but the new site has been a pain to use from day one.
― Douglas Adams, The Restaurant at the End of the Universe
They aren't shuffling everything (Facebook), making it slow and laggy (Reddit), making constant stupid changes (Quora), or throwing out features.
I'm genuinely asking, because how the fuck does that site make any money?
There are a lot of glitches (for weeks the answer button in a request to answer in notifications returned a 500 error), lots of trolls, lots of spammy questions, and the occasional decent piece of writing. The usual. I still don't think they have a test suite simply because they keep changing every little thing.
Quora makes money on advertising. A lot of the answers are actually paid adverts which are them promoted into your feed. Read closely, as often in those top 5 lists is the company that paid for the list to be written. So many of the top 5 to do travel answers were sponsored and promoted.
My first impression of it was: "Why have they turned the desktop version into the mobile version"? Newsfeed posts now in too-big-fontsize (but it's probably good for accessibility). Shortcuts on the left disappear when reading a group's stream. Etc etc moan-and-whinge-etc.
At first I thought they redesigned the site specifically to make me unhappy (because everything is about me). But a few days later "rooms" turned up ... so I assume the redesign was done - in part - to help accommodate this new Zoom-like functionality?
There's usually a good reason to change a site's look-and-feel. Have Facebook developers done any blog posts on the reasons why they redesigned, what choices they made, what new tech the redesign enables etc? Maybe learning about their journey will help me come to accept the new design more quickly.
I used to work at NCBI when I was graduate student at UMD, more than 25 years ago. Pub Med was just being invented. There was a thing called Medline (which had been a replacement to a thing called Medlars).
The guy I worked for was an MD/PhD (math) who was publishing papers on document retrieval and natural language search. Absolutely brilliant man. There was (and I’m sure there still is) a tremendous group of great scientists there. It was mind blowing work for a kid right out of college.
Two things that came out when I was there https://en.m.wikipedia.org/wiki/BLAST_(biotechnology) and https://en.m.wikipedia.org/wiki/Spouge%27s_approximation . The environment there, and how much the researchers loved there jobs almost made it seem like getting a PhD could be worth it.
(That being said I imagine the staff researchers are not the people doing the Web UX.)
#!/bin/sh
test -s max-PMID||echo 32446294 > max-PMID;read x < max-PMID;x=$((x-1));h=pubmed.ncbi.nlm.nih.gov;
test ${#x} -eq 8||exec echo weird max-PMID;sed -i "/test/s/echo [0-9]\{8\} /echo $x /" $0;
case $1 in update) mkfifo 1.fifo 2>/dev/null;test -p 1.fifo||exec echo need 1.fifo;
(grep "<title>PMID .* is not available" < 1.fifo|sed 1q|sed 's/<title>PMID //;s/ *//;s/ .*//;' >max-PMID)&
y=$((x+10000));seq $x $y|sed '$!s|.*|GET /&/ HTTP/1.1\r\nHost: '"$h"'\r\nConnection: keep-alive\r\n\r\n|;
$s|.*|GET /&/ HTTP/1.1\r\nHost: '"$h"'\r\nConnection: close\r\n\r\n|'|socat - ssl:$h:443 >1.fifo 2>/dev/null;
;;"")awk -v min=1 -v max=$x 'BEGIN{srand();printf "https://'$h'/" int(min+rand()*(max-min+1)) "/\n"}';esac #/bin/sh
test -s max-PMID||echo 32449615 > max-PMID;read x < max-PMID;h=pubmed.ncbi.nlm.nih.gov;
test ${#x} -eq 8||rm max-PMID;sed -i "s/[0-9]\{8\}/$x/" $0;
case $1 in update) mkfifo 1.fifo 2>/dev/null;test -p 1.fifo||exec echo need 1.fifo;
(grep "<title>PMID .* is not available" < 1.fifo|sed 1q|sed -n 's/<title>PMID //;s/ *//;s/ .*//;wmax-PMID')&
y=$((x+10000));seq $x $y|sed '$!s|.*|GET /&/ HTTP/1.1\r\nHost: '"$h"'\r\nConnection: keep-alive\r\n\r\n|;
$s|.*|GET /&/ HTTP/1.1\r\nHost: '"$h"'\r\nConnection: close\r\n\r\n|'|socat - ssl:$h:443 2>/dev/null|grep -o '<title>[^<]*' >1.fifo;
;;"")awk -v min=1 -v max=$((x-1)) 'BEGIN{srand();printf "https://'$h'/" int(min+rand()*(max-min+1)) "/\n"}';esacWe kept everything we liked about PubMed legacy and enhanced it with:
- A clear and easy to read interface - Additional information on articles (citations counts, journal scores…) - A pin function to avoid opening 1,000 tabs - The possibility to discuss articles
Tell us what you think in the chat so we can improve it!
We kept everything we liked about PubMed legacy and enhanced it with:
- A clear and easy to read interface - Additional information on articles (citations counts, journal scores…) - A pin function to avoid opening 1,000 tabs - The possibility to discuss articles
Tell us what you think!
It uses screen real estate well but it feels weird to read from top left to the bottom right of your screen before you scroll. This makes it much harder to skim papers
I haven't played with desktop site yet.
People can go on PubMed, find some bad article about 5G or fluoridation from a dubious journal, and then send it around social media. The nih.gov TLD gives the impression of official sanction to all kinds of garbage.