Conversation

Following up: several people mentioned the original 1987 Apple Human Interface Guidelines, which I'd not read. It's not a comprehensive primer on interface design, but it is an extraordinary read—a huge amount of detail on *why* things are as they are. And a great bibliography!
Quote Tweet
Why are there no "standard texts" on designing software interfaces? (or tell me I'm wrong?) If you want to learn to *build* software, there are excellent and complete texts on the subject. It's not just a tech-vs-art thing: there are standard texts on type, drawing, color, etc.
Show this thread
11
70
498
Replying to
Funny also to imagine this in a modern Apple text. One thing that really struck me at Apple was that none of my colleagues seemed to read for their work, either historic material or contemporary stuff. (Part of what was so interesting was that this often didn't seem to matter…)
Image
Image
7
15
115
Replying to
One of the original philosophies was that it’s safe to experiment (as a user). Of course, that’s not where things have ended up and many people still have a fear of messing up… as they should given the software quality they are working with.
7
Not sure it would matter—AFAICT his role is mostly about organizational design and operation, rather than meaningful creative direction or ideation. His team seems to deliver their best work when he's gotten out of their way (which to his credit he's often done).