JefRaskin
Latest
Aza Raskin shares Jef Raskin's 1981 memo on the genesis of the Macintosh
If you don't already know Jef Raskin's name, you should spend some time getting to know his work. His son, Aza Raskin, turned out to be a bit of a prodigy, eventually doing important and amazing work at Mozilla in the Labs department. Aza's latest endeavor is a company called Massive Health. His dad, Jef, was a true visionary in user experience and wrote a book called the Humane Interface, a must-read if you design interfaces for human beings. Oh, and Jef is largely credited with this whole "Macintosh" thing, often called the "father" of the Mac, even though he opposed the use of a mouse! So if you're steeped in Mac lore, it's a wonderful thing to see his son Aza posting Mac origin-story documents with the man's comments inline. Jef was quite opinionated, and it's worth reading comments he added to "Macintosh Project Genesis and History" -- a document he wrote in 1981. Read the story of the document, excerpts and the full thing at Fast Co.Design or check out the full thing with Jef's handwritten notes on the next page (sorry, a Flash embed from Scribd, so it won't work on iOS). The document makes clear why Apple chose to rigidly control the hardware in the Macintosh platform and sheds some light on key design considerations. The integrated monitor, for example, made it much easier to design a standard user interface, legible fonts and maintain consistency throughout the OS and third-party applications. Aza notes that Android currently suffers from issues similar to those that the Apple II line suffered from then: fragmentation. Although it's weird to think about now, I do remember radical display differences when going from my Apple II to my Laser 128 to my dad's Apple //c. Also, a standard set of hardware made everything from manuals to marketing easier. As the guy behind many manuals at Apple, Jef understood how good that would be. But the marketing? To quote Raskin: "The secret of mass marketing of software is having a very large and extremely uniform hardware/software base." I think anyone can understand how that fits into the current iOS strategy at Apple.
