I'm curious just how far down the rabiit hole you can take this philosiphy. Just how many APIs and programming interfaces and other interaction points of a computer can be eliminated or automated away or even made to adapt to user preferences? What would this mean for the divide between the Operating System and its Applications?
The Cooper Journal: The best interface is no interface
11–20 of 36 posts
Re: The Cooper Journal: The best interface is no interface
#12Earlier quoted context omitted.
First off, I liked the article. He's right in that visual UI should only be looked at after everything possible has been gleaned from process. As for TVs, I think most who are designing the interfaces are still stuck "inside the box". They need to take a couple steps back and learn how modern people use the interfaces. This is one of the main reasons I dropped cable and now feed my TV from a web-connected PC. The cab…
My grandfather, a regular country man, is horrorized by the amount of choices he has. Nowadays there is a remote for the TV with a lot of buttons, another for the video decoder, with more buttons, and another for the radio, with yes, more buttons. He was used to have a machine which worked upon being switched on. The TV had buttons labeled 1-10 for the ten channels. The radio only needed a dial and a volume slider. H…
In the days of simple on/off TVs, these didn't exist. I know they're not going to give up the Food Network, ESPN, Nickelodeon for the great-grandkids, CSI, etc. Things are more complicated now for a reason. When there were only 3 channels, you only needed one remote with 10 buttons on it. I agree that interfaces have gotten out of control (I can enter the menu on my TV without the remote, but I can't exit it?), but the reality is, you get features or you get simplicity. There's no way to control 3 or 4 disparate systems with all their capabilities with only 10 buttons and no on-screen interface.
Re: The Cooper Journal: The best interface is no interface
#13I'm curious just how far down the rabiit hole you can take this philosiphy. Just how many APIs and programming interfaces and other interaction points of a computer can be eliminated or automated away or even made to adapt to user preferences? What would this mean for the divide between the Operating System and its Applications?
That would completely eliminate the need for a UI or menu or remote.
Re: The Cooper Journal: The best interface is no interface
#14Earlier quoted context omitted.
My grandfather, a regular country man, is horrorized by the amount of choices he has. Nowadays there is a remote for the TV with a lot of buttons, another for the video decoder, with more buttons, and another for the radio, with yes, more buttons. He was used to have a machine which worked upon being switched on. The TV had buttons labeled 1-10 for the ten channels. The radio only needed a dial and a volume slider. H…
My grandparents always lament how complicated things are these days. They too just want a simple 1-10 and on/off remote. These do exist, but I keep reminding them why it's not possible for them: they have cable. And a DVR. And a DVD player. And a sound bar. In the days of simple on/off TVs, these didn't exist. I know they're not going to give up the Food Network, ESPN, Nickelodeon for the great-grandkids, CSI, etc. T…
Re: The Cooper Journal: The best interface is no interface
#15Re: The Cooper Journal: The best interface is no interface
#16"The best interface for a shovel is a hole where you need it"
Re: The Cooper Journal: The best interface is no interface
#17Apparently the best page is blank without JavaScript enabled, too.
Re: The Cooper Journal: The best interface is no interface
#18e.g. think about accounting applications:
You had trained data typists in the 60s, who typed the accounting records in a format, that can be directly processed in a batch oriented way.
You had 3270 terminals in the 70s, for trained typists, to enter the accounting data into a form, that was producing the records to be processed in a batch oriented way.
User interfaces become more interactive in the 80s, applications become personal, and there was no batch oriented processing anymore.
Most accounting software requires the use of the mouse now, so its no longer possible to use them for a trained typist, who prefers that her fingers stays on keyboard.
Lets step back:
My own home grown accounting software is written AWK. Its parsing a plain text in a markdown like syntax, and producing all papers I need for tax and accounting with a single "make". Calling ":wmake" is F2 in VI for me. The complete accounting system is 88 lines for invoices, 128 lines for monthly tax, 168 lines for annual tax. Its pure batch oriented, requires no database, and I'm using my preferred interface, the VI editor.
Re: The Cooper Journal: The best interface is no interface
#19At first I thought I would read a rant about current user interfaces, but the article turned out to be well thought, smartly written and, above all, it doesn't discuss interfaces _per se_. It goes up a meta level and proposes eliminating interfaces everywhere, because instead of helping people, they hinder the interaction. During the first few lines I had to convince myself that it is actually a good idea, but they a…
Re: The Cooper Journal: The best interface is no interface
#20Apparently the best page is blank without JavaScript enabled, too.