I was reading the wrong section of the required reading from SCAD’s online class; but the reading turned out the be a pretty cool section on how users interface with keys. And then the author (Jef Raskin) mentions something about the rationale for his design of one-button mouse:
My design for an interface based on a one-button mouse was refined and extended in discussions with many coworkers… and many adjustments were made based on observations made during user testing and during subsequent development. Some users do have difficulty both holding down a button and simultaneously moving a graphical input device… In the Macintosh deign, the problem was alleviated by having only one large button on the mouse, with low holding force and good tactile feedback. (p. 209)
So there we have it. A design from the 80s was effectively (and stubbornly) carried out well into 2005. But here’s the fun part: even though the book was published in 2000, Jef Raskin had already conceived many of the ideas in the new mouse that Apple introduced earlier this year.
A better mouse might have two buttons on top… a “Grab” button on the side that is activated by squeezing the mouse… Some mice at present have a wheel on top that is used primarily for scrolling. Better still would be a small trackball in that location. The mouse would control the position of the curser; the trackball could be used, for example, to manipulation objects or to make selections from menus that float with the curser. (p. 209)
Sound familiar? Here’s what Apple says about their mouse:
Meet the mouse that reinvented the wheel. The scroll wheel, that is. At $49, Mighty Mouse features the revolutionary Scroll Ball that lets you move anywhere inside a document, without lifting a finger. And with touch-sensitive technology concealed under the seamless top shell, you get the programability of a four-button mouse in a single-button design. Click, roll, squeeze and scroll. This mouse just aced the maze. ((c) Apple Computer)
Somebody give me $500,000 so that I can take the rest of the ideas in Jef Raskin’s book to market! I promise I won’t put all eggs in one basket.
Another interesting fact is something I learned from the database class last night. Apparently the idea of a “database” was conceived by E.F. Codd at IBM in the 70s. He published a paper that pretty much defined how all relational databases behaved today. But IBM didn’t really think the paper was worth the effort to development upon, so they simply shelved the idea (and there simply wasn’t enough computing power to run such design). So in the 80s, some guy came along and decided to implement the ideas in E.F. Codd’s paper, and Oracle was born. And Oracle’s been kicking IBM’s ass in the database market ever since.
Having good a idea ahead of its time is a bitch.