·
Five surviving snapshots—from the 1982 Apple IIe text interface to today’s multi-platform HIG—show what Apple asks interface designers to care about.
Select a ribbon to see how that topic changed.
The early transition is not the invention of human-centered design. It is the move from a keyboard-and-text grammar into a graphical object world; later editions repeatedly reorganize and expand that foundation.
The 1982 Apple IIe guide devotes nine measured pages to audiences, user profiles, early tests, direct observation, and iteration. The 1987 desktop book preserves the method but compresses it to one page.
“Begin your human interface design by identifying your target audience.”
“The primary test of the user interface is its success with users.”
The 1987 book has three broad chapters. The 1992 edition has eleven: principles and process remain, while menus, windows, dialogs, controls, icons, color, behavior, and language become independently navigable bodies of guidance.
1987 already insists that users decide whether an interface succeeds. In 1992, that idea becomes a sixteen-page design-and-development chapter with audience definition, task analysis, prototypes, observation, and iteration.
“The primary test of the user interface is its success with users.”
“Involve users throughout the design process and observe them working in their environment.”
The 1987 edition makes the curb-cut argument years before the term became common in software. The 1992 book retains disability guidance, calls it universal access, and places it beside worldwide compatibility and networked collaboration as general design considerations.
“Computers hold tremendous promise for people with many kinds of disabilities.”
“Providing universal access means creating products that all people can use, including people who have a disability.”
1987 treats icons as part of graphic communication and the desktop metaphor. In 1992 they receive a thirty-four-page chapter covering recognition, cultural limits, metaphor choice, families, sizes, bit depth, and testing.
“Simple design is good design. Don't clutter the screen with too many windows, overload the user with complex icons, or put dozens of buttons in a dialog box.”
“People often recognize pictures of things and understand them more quickly than they do verbal representations of the same things.”
The 1987 instruction is concise: write directly, plainly, and with a skilled writer. The 1992 chapter expands this into terminology, tone, alert messages, documentation, interactive help, and Balloon Help.
“Communicate with the user in concise and simple terms.”
“A good alert box message says what went wrong, why it went wrong, and what the user can do about it.”