Live data from Hacker News

The Same User Interface Mistakes Over and Over

prog21.dadgum.com

51–60 of 89 posts

Re: The Same User Interface Mistakes Over and Over

#51
The fact that those are the faults you think are the worst shows how entrenched bad UX is.

E.g. drop down menus are a fail.

If you read Raskin's "The Humane Interface" you can see a whole host more.

Raskin, Jef 2000.The Humane Interface, Addison-Wesley ISBN 0-201-37937-6

Re: The Same User Interface Mistakes Over and Over

#53
post #22
post #21

>>It's also not clear that the model of background apps requesting the user's attention works. How many iPhones have you seen with a red circle containing "23" on the home screen, indicating that 23 apps need updating...and it's been there for months? I would argue this is working as intended. The advantage of background notification rather than modal is that the user gets a choice. The user could very well decide th…

Agree. I avoid updating apps that are working satisfactorily because many later add ads or other annoying functions.

Mind you, there's a large difference between standalone apps (e.g. most casual games), and client-server apps. Standalone apps—sure, don't update, who cares.

But I don't begrudge the developer of a client-server app, that wants to change their server's API and then push an update to the client that speaks to the new API. Or, more to the point, I don't begrudge them if six months later they shut the old API down and the app stops working until I update. It's a client-server app in an ecosystem where updates are supposed to be automatic; of course it needs to be up-to-date to work. Would you expect to play e.g. an MMO without installing the updates before connecting to the server?

Re: The Same User Interface Mistakes Over and Over

#54
post #7

If you decide to study how to build bridges, you will start out with calculus, build a background in science of materials and then a guided tour of approaches to structure-building. In addition, you have to learn typical environmental factors. And, of course, there are workflow patterns and human factors involved in actually constructing a typical bridge. Oh, and sure, there will be a bit of CAD. Let's apply this met…

Meh. If you read The Design of Everyday Things and then look around, you see so many faults with the UI of physical things, even some which have been around for more than a century. A good example is packaging: "The Consumer Product Safety Commission estimated that attempts to open packaging caused about 6,500 emergency room visits in the U.S. in 2004."

>with the UI of physical things

That's not the building bridges level engineering that the parent talked about.

In fact, any designer/CAD hack in some factory can get his hands in building packages or other physical items, so the situation is mostly the same as the one the parent criticizes. In most countries you don't need to have an engineering degree to design a package container, kitchenware or a toy car -- at best an "industrial designer" degree will do.

Re: The Same User Interface Mistakes Over and Over

#55
post #33
post #26

Earlier quoted context omitted.

Lets say conservatively that 70% of Americans open at least one package a year, equalling 223,230,000 packages opened. 6,500 injuries is 0.0029%. Not bad I think.

0.0029% for injuries that require an emergency room visit, not injuries at all. Let's go for a conservative, 100:1 ratio of minor cuts vs injuries that make you want to spend a bunch of money on doctors, and we see that it's pretty darned dangerous. Dangerous enough that at work, we have mandatory training on how to open different kinds of packages safely! That said, the state of blisters has improved, precisely beca…

>0.0029% for injuries that require an emergency room visit, not injuries at all.

If you get an "emergency room visit" for trying to open a package, there's also some sort of idiocy involved.

I wonder if the level of E.R visits would for perfectly designed packages wouldn't be close or similar, because of idiocy.

Re: The Same User Interface Mistakes Over and Over

#56
post #46
post #36

Can we talk about search dialogs that are not actually dialog boxes ? I first saw it at netflix - instead of a search box in the upper right, there is a picture of the word search and if you click on that picture of the word search it becomes a textbox[1] that you can type into. As if that's not bad enough, the word "search" can turn into a textbox faster than it takes to fully load the control, which means you get t…

That's what Netflix got from using Reactjs. Facebook people search on mobile page version uses React too. It worked very well as a traditional AJAX search. Then they changed to to use React and now it takes a second or two to initialize and load the page (even it is in cache). And the search textbox doesn't feel like a native textbox, it's very laggy and shows inputs way too many milliseconds later. And on top of thi…

>That's what Netflix got from using Reactjs.

...for using Reactjs badly. IFTFW.

First, they could have had the item as a search box from the start, no need to make a label that when clicked turns into a search box.

>* If you have to refresh 90% of the search results page anyway, why use React? Building and diffing a VirtualDOM isn't cheap*

Actually it can be as cheap as directly changing the DOM with JS. And diffing can be just a single op e.g. when using an immutable data structure for their always changing part of the data.

It's just a change done crudely, not even non-optimized, because it doesn't need that much optimization anyway.

Re: The Same User Interface Mistakes Over and Over

#57
post #38
post #11

Earlier quoted context omitted.

I tend to rely on the Apple's UI guidelines. They have many hints that are applicable even for non-Apple apps. I remember Apple had a similar thing already back in 80s, which I found amazing. https://developer.apple.com/library/mac/documentation/UserEx...

Cycle through apps using command-tab. Cycle through a few times. See how it works. Now cycle through app-windows with command-` and see how that works .. completely differently .[1] So yes, even the wizards can get it wrong[2]. [1] command-tab has a proper "memory" allowing you to command-tab back and forth quickly between the two most recent apps. command-` is just ... weird. It sort of preserves sequence ... until…

>Not saying either is the right one - but they are both different, so one of them (as far as apple is concerned) is wrong.

Or maybe each of them is appropriate for the (different) tasks it has to do?

Re: The Same User Interface Mistakes Over and Over

#58

The fact that those are the faults you think are the worst shows how entrenched bad UX is. E.g. drop down menus are a fail. If you read Raskin's "The Humane Interface" you can see a whole host more. Raskin, Jef 2000.The Humane Interface, Addison-Wesley ISBN 0-201-37937-6

>If you read Raskin's "The Humane Interface" you can see a whole host more

Well, Raskin also has some bizarro ideas about what a good UI should be, and his later attempts of realizing one is not anything most people would want to use.

Re: The Same User Interface Mistakes Over and Over

#59
post #7

If you decide to study how to build bridges, you will start out with calculus, build a background in science of materials and then a guided tour of approaches to structure-building. In addition, you have to learn typical environmental factors. And, of course, there are workflow patterns and human factors involved in actually constructing a typical bridge. Oh, and sure, there will be a bit of CAD. Let's apply this met…

A bridge supporting a weight load of X in wind/water conditions Y is a testable thing.

A UI that is "easy to use", "intuitive", "has the things you use most front & center", etc, are all soft subjective terms. Even when you run stats over a population to try to find generic mediums, those overall expectations will change over time as well.

Re: The Same User Interface Mistakes Over and Over

#60
post #21

>>It's also not clear that the model of background apps requesting the user's attention works. How many iPhones have you seen with a red circle containing "23" on the home screen, indicating that 23 apps need updating...and it's been there for months? I would argue this is working as intended. The advantage of background notification rather than modal is that the user gets a choice. The user could very well decide th…

Also automatic application updating (default on since iOS8) mostly solves the problem for people who aren't choosy about updates.
Post reply on HN