Live data from Hacker News

The Same User Interface Mistakes Over and Over

prog21.dadgum.com

81–89 of 89 posts

Re: The Same User Interface Mistakes Over and Over

#81
My biggest complaint is regarding web sites/applications that basically ignore the existence of keyboards. Some of this comes from the UI toolkit that they're using, but it's pretty egregious. For just "brochure" web sites, it's not that big of a deal, but some are really, really bad about tabbing order, or tabbing at all, and certain controls don't work correctly without the mouse/touch.

Re: The Same User Interface Mistakes Over and Over

#82
post #15

Earlier quoted context omitted.

Material Design is just like Apple's guidelines. It's great for helping to create something that looks uniformly designed and not a hodge podge of UI gimmicks, helping design-ignorant coders create something that looks nice, and as you say it's easy to get management buy in, but is it actually good? Will following it actually reduce your count of UI mistakes? Personally I don't like it at all, and I've had many compl…

I agree. But I do not have the time to go back and do another degree on design. Try convincing people with money to shell out extra for someone with good design experience. I guess once we have millions of customers we might have to think about it - but small companies without much resources its hard to justify spending a lot of resources on good design.

Good design == lower churn, higher LTV.

Re: The Same User Interface Mistakes Over and Over

#83
post #58

Earlier quoted context omitted.

> 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.

I use Acme text editor which uses some of Raskin's ideas It is the best I have ever used https://en.wikipedia.org/wiki/Acme_%28text_editor%29

You, Rob Pike and 10 other people.

Re: The Same User Interface Mistakes Over and Over

#84
post #55

Earlier quoted context omitted.

> 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.

You've probably been downvoted (although, not be me) for using the term 'idiocy' which is a really unfair and derogatory accusation. I've cut myself on packaging before, definitely. I've probably done it in the past year. I am not 'an idiot'. ER visits could be for a number of indirect reasons; blood disorders that could prevent blood from clotting affect at least 6,500 people in the US. Just because the injury you'r…

>* I've cut myself on packaging before, definitely. I've probably done it in the past year. I am not 'an idiot'.*

Well, I've cut myself too. That's not the problem.

It's the E.R level injury though that I say implies some incompetence.

And if they have "blood disorders that could prevent blood from clotting", they shouldn't mindlessly be using knives and other sharp objects to open packaging.

Re: The Same User Interface Mistakes Over and Over

#85
post #83

Earlier quoted context omitted.

I use Acme text editor which uses some of Raskin's ideas It is the best I have ever used https://en.wikipedia.org/wiki/Acme_%28text_editor%29

You, Rob Pike and 10 other people.

mind yourself on that edge

or

not everyone can drive a Ferrari

Re: The Same User Interface Mistakes Over and Over

#86
post #80
post #18

Does anyone have enough experience with Tk and REBOL why these should be exemplar as far as UI and layout is concerned?

I was wondering the same thing. Reading the other answers, it seems like the reason the author thinks they're superior is that he can design interfaces using only code. (Not sure if that's the author's point or just the posters here.) I've had to use the apps that result from developers designing interfaces in code and I've had to read some of the code to do it, and in my experience it was all suboptimal. With a tool…

>> design interfaces using only code

The lines are blurred in Rebol because code is data and data is code.

>> the author seems to advocate that UIs should be disconnected from events

I don't think the author is advocating this because both TCL/TK & Rebol View rely on events.

Re: The Same User Interface Mistakes Over and Over

#87
post #8

was hoping you were going to give a standard resource where I can find alternatives for common bad designs

Check out "About Face" by Alan Cooper et al. A well respected interaction designer was so kind to give me her 1st edition many years ago and I still find myself coming back to it regularly. New and updated 4th edition: https://en.wikipedia.org/wiki/Special:BookSources/9781118766...

I had bought and read the 1st edition of About Face years ago. Thought it good generally. Might not have understood everything in it at the time. I remember him talking about "affordances". One point I thought was good, was his idea for a scroll bar with both the arrow heads at the same end of the bar, instead of at opposite ends. This saves you from having to move your mouse from one end of the bar to the other, to reverse scroll direction (since you have to click on either the up/left or down/right heads).

Like this (for a horizontal scroll bar):

=============================

instead of this:

Cool. Later I heard from someone that some OS/GUI platform actually has his improved version - I forget which.

Re: The Same User Interface Mistakes Over and Over

#88
post #87
post #8

Earlier quoted context omitted.

Check out "About Face" by Alan Cooper et al. A well respected interaction designer was so kind to give me her 1st edition many years ago and I still find myself coming back to it regularly. New and updated 4th edition: https://en.wikipedia.org/wiki/Special:BookSources/9781118766...

I had bought and read the 1st edition of About Face years ago. Thought it good generally. Might not have understood everything in it at the time. I remember him talking about "affordances". One point I thought was good, was his idea for a scroll bar with both the arrow heads at the same end of the bar, instead of at opposite ends. This saves you from having to move your mouse from one end of the bar to the other, to…

IIRC OSX had it at some point.
Post reply on HN