3 ms·
I would urge developers to also take a look at the early "Inside Macintosh" series, which tried to explain Apple's Human Interface Guidelines to programmers. Ta
by matthewdgreen 4y ago
I would urge developers to also take a look at the early "Inside Macintosh" series, which tried to explain Apple's Human Interface Guidelines to programmers. Take a particular look at Vol1-Chapter 2 [1] to see how hard Apple worked to explain how to design consistent and usable apps. All of this advice ("avoid modals", "group commands in menus") seems trivial to us now: that's how GUIs have worked for most of our lives. But prior to Mac most apps looked like vim. These ideas had to be designed and then taught, and Apple spent a huge amount of effort on those books.
[1] https://vintageapple.org/inside_o/pdf/Inside_Macintosh_Volume_I_1985.pdf https://vintageapple.org/inside_o/pdf/Inside_Macintosh_Volum...
- ghaff 4y agoAlso worth reading is Tog on Interface by an early Apple employee who was Apple's Human Interface Evangelist in that period. One particularly interesting essay goes into the issues associated with the way that developers are used to dealing with abstract models in a way that many users aren't. (He bases his argument in part of Meyers Briggs which is astrology to some degree--but the basic point stands.)