Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Laws of UX

lawsofux.com

Post reply on HN
Print view View original

91–100 of 114 posts

Re: Laws of UX

#91

Post by AtNightWeCode »

nelsonenzo wrote: post #2

These seem like theories, not laws. And imho, some of it is very wrong, such as: > Purposefully adding a delay to a process can actually increase its perceived value and instill a sense of trust, even when the process itself actually takes much less time.

Yes, it is incorrect. Some UX designs even try to make you feel like something happens instantly when it is not. Best example I can think of is that Spotify used to have this animation on the play button that was just there to hide the delay between click and play.

Re: Laws of UX

#92

Post by [deleted] »

JohnFen wrote: post #54
pickingdinner wrote: post #36

Earlier quoted context omitted.

This is just math, so I will continue to elaborate. Mouse clicks and distance are two of the most basic metrics. And straight forward. So why wouldn't you optimize there? But what you're referring to is that which can offset and add to those metrics. "Mouse click" in and of itself means nothing in the context of the program. So it's the "other stuff" that pushes against the goal being accomplished in 1 click. So the…

> Mouse clicks and distance are two of the most basic metrics. And straight forward. So why wouldn't you optimize there? You might, but to do so based solely on those metrics is a mistake. That's because those metrics don't fully capture what makes a UI efficient for human use. Other things, like cognitive load, are more important. Does it matter if it only takes two clicks to do a thing if that usage path isn't one…

[deleted]

Re: Laws of UX

#93

Post by Jemm »

Noticing that most websites are designed for mobile now and barely work on desktop especially if zoomed in or using accessibility features.

Sticky headers take up half the page.

Margins are too wide for the browser

Images are way too big compared to text size

Images don't fit on the page no matter what zoom level you use.

Re: Laws of UX

#94

Post by somat »

carlosjobim wrote: post #14
lexicality wrote: post #4

Earlier quoted context omitted.

That one is actually genuinely true and why so many price comparison and search websites artificially load slowly with fancy loading screens.

I think that's more of pseudo-science. I've never heard anybody express any distrust for a service just because it's fast. Let's say you go to a store and ask if they have a certain product. The clerk says "Sure, here it is". Is that worse than saying "Hmmm, I have to check in the warehouse first"?

On the other hand I can imagine there being some sort of study that claims that having to "check the warehouse" makes the client now invested in the process and more likely to complete the sale.

I get it, sales and marketing are an essential part of doing business, you will not have a business if you can't sell anything. But it is an inherently evil practice, the whole goal is to coerce somebody into doing something they would not have other wise done. When kept to a moderate amount this is not a problem, the business sells things the customer gets things, everybody is happy. But sometime the marketing department can push thing to a very unhealthy level, psychological manipulation, dark patterns, obsessive tracking, etc.

Re: Laws of UX

#95

Post by lexicality »

AtNightWeCode wrote: post #89
lexicality wrote: post #4

Earlier quoted context omitted.

That one is actually genuinely true and why so many price comparison and search websites artificially load slowly with fancy loading screens.

BS. Google have shown that any time loss in any stage of any payment process directly affect conversion rates.

Payment process is different.

This is all about implying serious work and complexity is taking place for some interaction there the user thinks there should be some.

PayPal used to have an entirely artificial five second wait between the user hitting "log in" and the browser sending the request because it raised perceived security in user testing.

Many banking apps will display "establishing secure connection" for a while for the same reason.

(Possibly paypal still have an artificial delay, but it's hard to tell given how badly the site works these days)

Re: Laws of UX

#96

Post by drekipus »

jonny_eh wrote: post #82
chrstphrknwtn wrote: post #73

Earlier quoted context omitted.

No, it's important that every single element vertically slide and fade in as I scroll the page. How am I supposed to know this is "design".

That's the "chrstphrknwtn principal", use whichever principal best applies.

This is the "jonny_eh meta-principle" at work! Finally see it with my own eyes!

Re: Laws of UX

#98

Post by kazinator »

JohnFen wrote: post #35
JohnMakin wrote: post #34

I would like to see more support in UI/UX for people who are not neurotypical. Or, customizable interfaces to support people with disabilities. When you build for the common denominator, these people get left out.

When you build for the common denominator, a huge number of people are left out, including those with disabilities. > customizable interfaces to support people with disabilities. Customizable interfaces are the only real solution -- not just for people with disabilities, but for everybody. There are a number of websites and applications that I stopped using because of UX choices I am allergic to. If they were configu…

When you build for the common denominator, people with brains often get left out.

Re: Laws of UX

#99

Post by _thisdot »

thealchemistdev wrote: post #30
nelsonenzo wrote: post #2

These seem like theories, not laws. And imho, some of it is very wrong, such as: > Purposefully adding a delay to a process can actually increase its perceived value and instill a sense of trust, even when the process itself actually takes much less time.

I experienced this first hand with the manual sync button on one of my apps. I got feedback stating it didn't work when, in reality, there was no work to be done and the interface didn't have time to display 'syncing' before it finished. The solution was to add a 50-300ms delay before the network request. Why? Because feelings and perception matter more than facts.

Perceived loading time was a matter of debate during the NextJS vs RemixJS thing. RemixJS argued for fast loading time, while NextJS argued for perceived loading time.

Remix would show a white screen and two seconds later have everything ready. Next would show the header and a loader first then gradually over the course of 3-5 seconds have everything ready.

Re: Laws of UX

#100

Post by anste »

Every time I see this site it still amuses me that despite all the valuable UX information, it is very annoying to use on a desktop because it feels like it was designed entirely for tablets or phones.
Post reply on HN