Live data from Hacker News

The best interface is no interface

cooper.com

41–50 of 93 posts

Re: The best interface is no interface

#41

Tiny point: the article incorrectly implies chkntfs and atmadm were original early 1980's DOS commands, but they were circa 1990's.

Not to mention that it equates all CLI's with that horrible, no-tab-completion abomination that was the DOS command prompt. Sure, the commands in UNIX (and variants) were cryptic, but at least you could have real filenames (not that 8.3 nonsense) and do real programming with the shell, pipes, job control, and of course the already mentioned tab-completion. If you don't understand why some people still love the CLI, you probably haven't used a good one, or don't understand the power a good one gives you. DOS CLI was to UNIX CLI what Win95 was to OS/2 multitasking.

Re: The best interface is no interface

#42

Minor details aside, this is a spot-on analysis in the grand scheme of things. Computers should be doing more for us. They're smart, they're good at logic, they can make decisions. It's our job as programmers to make the do more and allow us to do less. I'm tired of complexity. I don't want a car that has a touch screen—I want one with a knob that's tactile and has a blue-to-red gradient that makes sense and only con…

I don't want a car that has a touch screen

Hell yes. Whoever decided to put touchscreens into cars deserves the Darwin Award.

We live in a bit of an unfortunate age where perfectly time-tested interfaces are replaced with inferior touch-controls left and right, just because "we can".

This applies even to the canonical application; the phone. It's great how many things we can do on our phones now, but the core feature (telephony) has suffered badly. I can't take a call without looking at it anymore, much less place one. In the winter every incoming call turns into a little challenge (how quickly can I rid of that glove without dropping my precious $600 slab-of-glass onto the icy concrete?)

Rewind to the 1990s. Many people could tap an entire SMS on their Nokia without taking it out of the pocket. We could dial numbers without looking because we knew a contact is "four taps down" in the address book, and the buttons gave us a reassuring "click" when they were pressed.

The industry needs to re-discover tactile feedback and predictable latency as desirable traits. Early androids had a jog-dial (sony) and dedicated camera-buttons (HTC), but they largely disappeared for stupid reasons.

I really can't wait for Apple to re-"invent" physical controls in one of their future models. Perhaps the telephony-experience on our expensive pocket-computers will then finally catch up to what we had 20 years ago...

Re: The best interface is no interface

#43
post #38

Earlier quoted context omitted.

>2. Using AI is a "step 2: ???" solution, and the flaw with it is best exemplified by the columnist who bought a pregnancy book for a pregnant friend on Amazon Flaws like this might exist right now, but that's really a "bug". It's a failure on our part (the software designers and engineers) to build a system that actually works for the human . So sometimes when we try to make our software smart, it ends up being [mad…

Doesn't "provide better context" just push the problem one turtle away? How could I communicate to the website that the item for which I'm shopping is for a friend, not for me, and that I don't want the current actions to figure into future adaptive behaviour? Perhaps a checkbox? But now we're adding interface, which we were trying to eliminate in the first place. I suggest that this is an intractable problem just be…

>Doesn't "provide better context" just push the problem one turtle away? How could I communicate to the website that the item for which I'm shopping is for a friend, not for me, and that I don't want the current actions to figure into future adaptive behaviour?

That's part of the implementation, again, I think. It would be silly for the implementation to treat just once instance of a behaviour so seriously. If the user buys it once, but then never shows any interest in such products again, then they should slowly be ranked less and less relevant. If the user instead continued to purchase or look at baby items, then the system could have more certainty of desire in them. Again, it's not just the products themselves, but the behaviour surrounding them. Temporal context is important, too.

I agree fully that just heaping on more interface for "special cases" is a bad idea. We just need to be smarter about...how our software is smart.

Re: The best interface is no interface

#44
While no interface is better, it is not always the simplest or the most utilitarian.

The Mercedes proximity based, keyless entry system is actually a complex digital abstraction over a mechanical key/lock.

Mercedes has to address a bunch of security concerns such as preventing an adversary from sniffing my key information through my jacket pocket, digitally cracking codes, etc. Since the system tries to protect you from locking your key in the car, more technological components need to be thrown into the mix to detect if the key is inside the car. If the driver has to reach into his pocket to turn on the ignition it would defeat the purpose of going "keyless" so presumably the ignition system also gets a few layers of complexity. The cost of whole system would also go up. Repair and maintenance don't sound so appealing either. The whole thing can fail in a lot more ways.

I am not inferring it's a bad idea. It very well might become commoditized technology some time in the future and pave the way for other interesting possibilities.

I prefer utilitarian design which is more concerned with simplicity through and through rather than just minimizing the footprint for the user interface.

Re: The best interface is no interface

#45
post #36

I found the article somewhat light on useful examples; however the premise is very interesting, so I would like to bring a couple of my own examples to the table : In a restaurant named "The Herb Farm" in Seattle area you don't pay when you eat, you pay before the dinner, when making a reservation by phone (the menu is prix-fixe). So when you're done eating you just walk out - no waiting for the check, no computing t…

I'm flattered. And thankful to have my essay be voted to #3 on Hacker News.

I'm speaking at SXSW 2013 about "the best interface is not interface." This is an evolving idea, and I hope to have some gaps filled by the time I speak in March. So thank you all for your feedback.

I'm collecting more examples at nointerface.tumblr.com. It's meant to be an inspiration site for people interested in this movement. It's an idea Tumblr. And starting mid-January, I'm hoping to have two new posts a week, but that's mostly dependent on finding great examples. So, please tweet any to @goldenkrishna...Il give credit, of course.

Re: The best interface is no interface

#46
post #42

Minor details aside, this is a spot-on analysis in the grand scheme of things. Computers should be doing more for us. They're smart, they're good at logic, they can make decisions. It's our job as programmers to make the do more and allow us to do less. I'm tired of complexity. I don't want a car that has a touch screen—I want one with a knob that's tactile and has a blue-to-red gradient that makes sense and only con…

I don't want a car that has a touch screen Hell yes. Whoever decided to put touchscreens into cars deserves the Darwin Award. We live in a bit of an unfortunate age where perfectly time-tested interfaces are replaced with inferior touch-controls left and right, just because "we can". This applies even to the canonical application; the phone. It's great how many things we can do on our phones now, but the core feature…

I totally agree with everything you wrote, but since it is going to be a while yet before the industry learns any of these lessons...

You can pretty easily turn any set of gloves into touch-capable gloves using a small amount of conductive thread and sewing it through the pad area on the primary finger you use for touch.

Re: The best interface is no interface

#47
post #26

I have two criticisms of the article: 1. Every story is a 'just so' story where the way the system works is exactly the way the user wants the system to work. Great, it's like putting a button front and center on your app and the user wants to push that button and look! It's right there! Awesome. Except I don't want to push that button, I want to push the other button that's now hidden away because the designer is st…

With the Amazon example, just remember that they don't show you product suggestions for help you, they are showing them to sell more product.

If on average the technique works across the entire customer base, then they will apply it.

While it would certainly be better if they were more accurate in that fringe case as well, if it would take 4x the effort to eek out a 20% improvement, that might not be a good trade off for them.

Re: The best interface is no interface

#48
post #36

I found the article somewhat light on useful examples; however the premise is very interesting, so I would like to bring a couple of my own examples to the table : In a restaurant named "The Herb Farm" in Seattle area you don't pay when you eat, you pay before the dinner, when making a reservation by phone (the menu is prix-fixe). So when you're done eating you just walk out - no waiting for the check, no computing t…

> So when you're done eating you just walk out - no waiting for the check, no computing tips, none of that nonsense that should not be part of a pleasant dinner.

I dunno. If service and food was good, I like commending the staff about it. It would feel awkward to approach the staff without any reason, because I paid earlier already. Granted, I think this is the metaphor breaking. Interacting with the staff isn't just an interface, it's interacting with humans.

Re: The best interface is no interface

#49
post #26

I have two criticisms of the article: 1. Every story is a 'just so' story where the way the system works is exactly the way the user wants the system to work. Great, it's like putting a button front and center on your app and the user wants to push that button and look! It's right there! Awesome. Except I don't want to push that button, I want to push the other button that's now hidden away because the designer is st…

I am wondering if the unix shell is the no UI approach to the first problem. The unix shell doesn't provide a discoverable, nice interface. On the other hand, it is a minimalist interface which caters the task "Manipulate files in a multitude of ways" very well.

Re: The best interface is no interface

#50
post #36

I found the article somewhat light on useful examples; however the premise is very interesting, so I would like to bring a couple of my own examples to the table : In a restaurant named "The Herb Farm" in Seattle area you don't pay when you eat, you pay before the dinner, when making a reservation by phone (the menu is prix-fixe). So when you're done eating you just walk out - no waiting for the check, no computing t…

Your first example doesn't make sense to me. Why is the restaurant optimizing for the leaving experience? They should be optimizing for the eating experience. Like deciding to get an extra appetizer because the people you're with got one that looks really good. Or deciding to break your diet and get the dessert anyways.
Post reply on HN