Slashdot Mirror
Tangible Interfaces for Computers
Jesrad writes "A friend pointed me to this impressive demonstration of the SenseTable by James Patten, of the Tangible Media Group project of the MIT. This project aims at conceiving better human-machine interfaces by using the concept of physical objects that the user can manipulate, to represent abstract computer data and commands. The device looks and works a lot like what was envisioned in Minority Report, it uses pressure to track blocks on a sensitive surface, and feeds back to the user by superimposing graphical data. Want to change the volume of your MP3 player? Just put a block on it and turn like you would a radio knob. Menus and commands are accessed by moving a block along command hierarchy, represented in a simple tree, or by touching the command's name. So far it only lacks a device for text input, like a keyboard, but maybe voice recognition will replace it?"
While various varieties of tangible interfaces might be useful in specific circumstances, the typical user doesn't want more crap on their desk. They want a flat, easily positioned, brillant screen (or three). They want a keyboard (which could be virtual, but most people prefer some tactile feedback for typing). They want something for pointing (which could be a glove, a mouse, entirely virtual, ...) They don't want a metaphor that looks like Play-School.
So far it only lacks a device for text input, like a keyboard, but maybe voice recognition will replace it?
I talk to my computer enough as it is. The day that it actually listens to me is that day that I'll have to rebuild it every other week, and red will be the day when it starts talking back to me.
I can understand why some people are appalled by tangible interface concepts. These are the same people that refered to GUIs as WIMPs (Windows, Icons, Menus, and Pointers). For some people, a command line, keyboard-coded interface just works. But it is not the best interface for everyone or every application.
1) Media creation: Who still creates CAD drawings with a keyboard only? I used some early versions of Autocad that where keyboard-only -- they sucked. Sometimes a tangible pointer with a 1-to-1 interface mapping between a 2-D surface and the screen is superior. For artists, the use of an LCD graphics pad and pressure-sensitive stylus means much higher productivity and finer control. (I've even scene academic research suggesting that a two-mouse interface could improve productivity.)
2) Mapping to the Realworld: Go aboard an aircraft carrier and look at how they keep track of flight-deck operations. A miniature replica of the flight deck and miniature aircraft provide an intuitive 1-to-1 mapping between the model and the real-world. I'd bet that they could improve flight deck operations if those little aircraft moved automatically to reflect actual locations and if manual movements of aircraft spawned automatic commands to flight deck personel.
3) Multiuser interfaces: the demos of MIT's system that I have seen (a business-oriented supply chain visualization tool) leverage the table interface for multi-user applications. With the table, anyone around it can reach over and move a block. And everyone can easily see who moved the block.
The power of tangible interfaces is that they can help create a more literal mapping between a digital artifact and the real-world. Sometimes less abstraction leads to better ease-of-use.
Two wrongs don't make a right, but three lefts do.
number sign bach back back back hash back #include lessthan back ;
int mane back maine back main bracket back ( int argh! see back back a r g c commet back , char star back ** a r g v ) brace back {
print f ( quote back "hello world") semicolon back
] no not that brace the other one back back back back back back back back }