"Interface-Free" Touch Screen at TED

Down8 writes, "Jeff Han, an NYU researcher, has recently shown off his 'interface free' touch screen technology at the TEDTalks in Monterey. Some sweet innovation that I hope makes it to the mainstream soon." The photo manipulation interface is reminiscent of "Minority Report."

Comments

Interface-free?

[WilliamSChips]

How do you not have an interface?

Re:Interface-free?

[Atlantis-Rising]

I took a gander at that book, and right away as I skimmed the amazon page, I noticed problems. He may be a wonderful cognitive psychologist, but he's no technocrat.

The whole "Why shouldn't my computer take three nanoseconds to turn on, read my mind, and then never ever have errors!!!?!?one1" thing is a very amateur approach to the problem, if you ask me. Sure, it would be nice, but I'm absolutely sure it's technically impossible.

To be more specific:
"There has never been any technical reason for a computer to take more than a few seconds to begin operation when it is turned on."
I can name half a dozen; power consumption for suspend to RAM, system process cleanup for suspend to disk, disk space storage for suspend to disk, driver software that doesn't gracefully handle failing down to a hibernate state, plug-and-play hardware detection on bootup... not to mention the whole raft of problems that occur when users never shut down and clog their system up by never ending processes.

The problem with the view he espouses is that it practically requires a suspend-state, when users aren't good with suspend states. It wasn't until Windows XP and the relatively modern (last three or four years) (okay don't flame me I'm sure SOMEWHERE there was a build that had really optimal suspend, but I couldn't find it) linux systems that suspend really started working, and even so, your device drivers really depend on when you can suspend the system and how it restores.

For example, when I tested Vista on my laptop, the base sound driver would for some reason kill the audio after restore from suspend. It just wouldn't make any noise until it rebooted. When I upgraded the driver, it went away.

It is, in fact, only recently that we have had flashmem and the concept of keeping your 'bootfiles' on a seperate flash partition to read from for a quick boot has been a realistic and close to mainstream idea for the desktop.

The same thing comes up here.
"Why should you have to double-click anything? What does Ctrl+D mean one thing in one program and a completely different thing in another? And what's the point of the Yes/No confirmation if the user is in the habit of clicking Yes without thinking about it?"
All of those things make sense in the context they are being used in, and they're relatively intuitive. After all, it's not the programmers fault the user is an idiot, especially with something as simple as a yes/no dialog box, as long as the dialog box is written in language comprehensible for the designed userbase.

Re:This is a very interesting set up

[jpardey]

Oh no! Children may use conventional tools, rather than futuristic things that are not in production yet, and probably won't be for 10+ years! When will we ever learn?

Interfaces are natural

[tygt]

I realize that the point of this (TFA) is about trying to make things more intuitive and natural. But, as others have pointed out in other words, interfaces are a natural aspect of life.

I have an interface in front of me right now. I have pen, paper; I've got a camera... if I want to record a visual of something, I have to pick up my camera. Never mind that the camera has one of these "non-intuitive interfaces" that we (rather, the article) are trying to remove, I still have to do something to get it done. Anything that I do interfaces with reality.

One of the goals of the iconic desktop originally was to duplicate the real desktop in some fashion to make things simpler for humans to interact with their work on a computer, so that there wouldn't be too much of a translation layer to build between real and virtual work. Similarly, some try to implement handwriting recognition to remove the interface of the keyboard from the writing process.... until they realize that geeks like us can't write for crap and can type ten times faster as well.

Regardless, of course, there's got to be some way to tell the computer that you actually want to resize the strange hand-like object on that screen the guy had (I think it was a hand, my sound was off and I lost interest rapidly) rather than add to the drawing. There's got to be some way to change modes, as he did between drawing the outline, getting it filled in, and then moving it around - that's all interface. Sure, it looked sweet that there wasn't any menu pull-down happening, no mouse, but really, you've got a pretty damn simple application that can be manipulated in this fashion.

Do anything complex, and you'll have to have a more complex interface suddenly.

"Computer... Computer... (McCoy hands Scotty the mouse) Aye. Hello computer." -- Scotty

Even talking to a computer would be an interface..... a pretty complex one, though definitely one that could be considered intuitive, if you could use your chosen language for commanding it rather than some cryptic "ok, list the files, sort by date then name.... uh.... ok that one no that shit fucking computer where's my mouse"