This is the origin origin of the entire Apple design library, and even of all graphical interface design. Two historic classics: · 1987“Apple Human Interface Guidelines: The Apple Desktop Interface” (164 pages) — the first official HIG, which defined the desktop GUI for Macintosh/Apple II and proposed 10 human interface principles. · 1992“Macintosh Human Interface Guidelines” (418 pages, 11 chapters) — the expanded complete edition, which increased the number of principles to 12, and provided complete component specifications for menus, windows, dialog boxes, controls, icons, colors, and more.
What is striking: these principles laid down in 1987 live on almost word for word in today's Apple HIG Design Principles and Mental Models (12 Core Principles / Fluid Interfaces / Intentional Design / Multisensory / ML Experiences) in(Feedback/Consistency/Direct Manipulation/User Control…). Reading this document is for understanding "why the modern HIG looks the way it does".
I. The 12 Human Interface Design Principles
The 1987 edition had 10 principles; the 1992 edition added the 11th and 12th. This is the "constitution" of all GUI design.
| # | Principle | Essence of the original wording (bilingual) |
|---|---|---|
| 1 | Real-world Metaphors | "Use concrete metaphors and make them plain"(Use concrete metaphors and explain them clearly, so users can bring real-world expectations to the computer.) The desktop itself is the primary metaphor; but metaphors do not need to be taken to their logical extreme (a scroll bar only loosely resembles a scroll). |
| 2 | Direct Manipulation | "Users want to feel that they are in charge"(Users should feel they are in control of the computer.) Physical actions should have physical results plus feedback (keys click, documents are dragged to the Trash); visual effects let people know an operation is being performed. "Why shouldn't using a computer be fun?" |
| 3 | See-and-Point (rather than Memorize-and-Type) | "Users rely on recognition, not recall"(Rely on recognition rather than recall.) Action = noun followed by verb ("Hey you—do this"); two paradigms: select the object first then choose the action (full menu listing) / drag an object onto another object (drag an icon into the Trash). Keyboard shortcuts are supplements, not replacements. The command line forces users to memorize and occupies their attention with the computer's demands. |
| 4 | Consistency | "Consistency should be valued above idiosyncratic cleverness"(Consistency takes priority over clever novelty.) Consistency within an app + consistency across apps allows skills to transfer; sometimes one should give up "a new solution that fits a specific situation better" in exchange for "a slightly inferior but more universal solution". |
| 5 | WYSIWYG (What You See Is What You Get) | "There should be no secrets from the user"(No secrets from the user.) What is on screen = the final printed output; users control content and layout, and the computer displays results directly with no need for mental guesswork. |
| 6 | User Control | "The user, not the computer, initiates and controls all actions"(The user, not the computer, initiates and controls everything.) It rejects the idea of "the computer as protector" that only offers options it judges to be "good"; risky operations should give warnings but allow the user to proceed after confirmation (protecting novices without taking away control). |
| 7 | Feedback and Dialog | "Keep the user informed. Provide immediate feedback." Provide immediate confirmation for operations; explain delays (when / why / how long); use the user's vocabulary, not the programmer's. |
| 8 | Forgiveness | "Users make mistakes; forgive them." Users learn by exploring (they don't like reading manuals); make operations as reversible as possible, and clearly notify users when an operation is irreversible;alerts should appear very rarely — if users are bombarded with warnings, it means the program's design is flawed. |
| 9 | Perceived Stability | "It is the illusion of stability that is important"(What matters is the stable "illusion", not strict physical stability.) Provide visual stability (fixed graphics such as the menu bar / window borders) + conceptual stability (a limited set of objects + a limited set of actions);unavailable actions should be grayed out rather than removed; give users reliable "landmarks". |
| 10 | Aesthetic Integrity | "Different things look different on the screen." Visual clutter / ugliness undermines efficiency; users should be able to control appearance to express individuality;"Messes are acceptable only if the user makes them—applications aren't allowed this freedom"(mess can be made by the user; the app does not have that freedom). |
| 11 | Modelessness(Added in 1992) | Let users do any (reasonable) thing at any time as much as possible; don't trap users in a mode they cannot get out of. |
| 12 | Knowledge of Your Audience(Added in 1992) | Design starting from understanding users and identifying their needs; this principle puts "people-centeredness" upfront as the starting point of design. |
II. Principles of Graphic Communication
"Good design must communicate, not just dazzle. It must inform, not just impress."(Good design should communicate, not just dazzle; it should inform, not just shock.)
- Visual Consistency: build a trustworthy environment for users;photorealism is not necessary — well-designed symbols / cartoons convey meaning better than fully realistic graphics.
- Simplicity: "Simple design is good design." Don't pile on too many windows / complex icons / dozens of buttons; icon menus are "the basic language of communication between user and computer", and messages must be simple.
- Clarity: start from understanding "the user's situation / the problem to be solved";sometimes text is better than graphics; test on real users (not peers); the most important parts should be seen first; use animation sparingly to guide attention.
III. Why This Document Is Worth Reading (Historical Significance)
· Foundational: After the 1984 Mac launch, this 1987 document was the industry's first systematic GUI design specification, which codified "desktop metaphor + direct manipulation + WYSIWYG" into followable principles, influencing every operating system that came after (including Windows). · Astonishing persistence: Compare it with today's Apple HIG Design Principles and Mental Models (12 Core Principles / Fluid Interfaces / Intentional Design / Multisensory / ML Experiences) — Feedback / Consistency / Direct Manipulation / User Control / Forgiveness are retained almost verbatim; only the means of expression have evolved from "desktop/mouse" to "touch/gestures/spatial".Good principles are universal and timeless(which is exactly what the modern HIG 12 principles article repeatedly emphasizes). · Lineage of evolution: 1987 (10 principles · desktop) → 1992 (12 principles · complete component specifications) → … → modern HIG (multi-platform · Liquid Glass · spatial computing). Modelessness later faded out (due to the return of modal design in iOS), but the spirit of the remaining 11 principles endures. · Usage for PMs: When you are stuck on "is this interaction right?", going back to these 12 original principles often lets you judge at a glance (for example, "this irreversible operation gives no warning" violates Forgiveness, "this mode traps the user" violates Modelessness).
IV. Complete Structure of the 1992 Edition (11 Chapters)
The 1992 *Macintosh HIG* is much larger than the 1987 edition; in addition to the 12 principles, it also provides complete component-level specifications —this is the distant ancestor of the modern Apple HIG Component Decision Manual (63 Components · When to Use Which) component manual: Ch1 Human Interface Principles / Ch2 General Design Considerations / Ch3 Development Process / Ch4 Menus / Ch5 Windows / Ch6 Dialog Boxes / Ch7 Controls / Ch8 Icons / Ch9 Color / Ch10 Behavior / Ch11 Language (Copywriting).
Sourced from two historical PDFs (1987 164 pages + 1992 418 pages = all 582 pages read,pdftotext text-extracted PDF body text). For the modern version of these principles, see Apple HIG Design Principles and Mental Models (12 Core Principles / Fluid Interfaces / Intentional Design / Multisensory / ML Experiences); for the modern component manual, see Apple HIG Component Decision Manual (63 Components · When to Use Which). The original files of the two PDFs are in sources (gitignore, retained locally).