The river of Apple’s interface guidelines

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.

The written lineage begins in 1978–79; this river starts with the oldest surviving standalone guide in the same Apple II lineage. The 1982 bank measures only its interface half, and 2008 combines the Mac and iPhone books. Measurements and short excerpts only. See every source.

One pixel represents the same number of words in every edition, revealing total growth.

Select a ribbon to see how that topic changed.

Attention by topic in the 1982, 1987, 1992, 2008, and current Apple interface guidelines — absolute scale One vertical pixel represents the same number of words in every edition; total bank height shows growth. Color describes how the guidance changed at each transition. Principles: held, 1982 to 1987 Design process: held, 1982 to 1987 Access & worldwide use: arrived, 1982 to 1987 Menus: reshaped, 1982 to 1987 Windows: arrived, 1982 to 1987 Dialogs & controls: reshaped, 1982 to 1987 Icons: arrived, 1982 to 1987 Visual system: reshaped, 1982 to 1987 Input & behavior: reshaped, 1982 to 1987 Language & help: held, 1982 to 1987 Principles: held, 1987 to 1992 Design process: expanded, 1987 to 1992 Access & worldwide use: expanded, 1987 to 1992 Menus: expanded, 1987 to 1992 Windows: held, 1987 to 1992 Dialogs & controls: expanded, 1987 to 1992 Icons: expanded, 1987 to 1992 Visual system: reshaped, 1987 to 1992 Input & behavior: held, 1987 to 1992 Language & help: expanded, 1987 to 1992 Principles: held, 1992 to 2008 Design process: held, 1992 to 2008 Access & worldwide use: held, 1992 to 2008 Menus: held, 1992 to 2008 Windows: reshaped, 1992 to 2008 Dialogs & controls: expanded, 1992 to 2008 Icons: reshaped, 1992 to 2008 Visual system: expanded, 1992 to 2008 Input & behavior: reshaped, 1992 to 2008 Language & help: reshaped, 1992 to 2008 Platforms & technologies: arrived, 1992 to 2008 Principles: held, 2008 to current Design process: dissolved, 2008 to current Access & worldwide use: expanded, 2008 to current Menus: held, 2008 to current Windows: reshaped, 2008 to current Dialogs & controls: held, 2008 to current Icons: reshaped, 2008 to current Visual system: expanded, 2008 to current Input & behavior: reshaped, 2008 to current Language & help: reshaped, 2008 to current Platforms & technologies: expanded, 2008 to current 1982 10,975 words Principles 2,141 Design process 2,882 Menus 606 Dialogs & controls 2,370 Visual system 308 Input & behavior 1,890 Language & help 778 1987 37,314 words Principles 4,385 Design process 367 Access & worldwide use 2,075 Menus 8,405 Windows 5,112 Dialogs & controls 3,167 Icons 1,083 Visual system 2,341 Input & behavior 10,102 Language & help 277 1992 74,158 words Principles 3,725 Design process 4,492 Access & worldwide use 4,338 Menus 15,355 Windows 8,449 Dialogs & controls 12,779 Icons 6,890 Visual system 2,150 Input & behavior 10,395 Language & help 5,585 2008 141,380 words Mac 110,753 · iPhone 30,627 Principles 13,597 Design process 4,463 Access & worldwide use 2,193 Menus 8,363 Windows 16,400 Dialogs & controls 41,921 Icons 9,797 Visual system 3,925 Input & behavior 15,510 Language & help 4,092 Platforms & technologies 21,119 Today 207,459 words Principles 1,141 Access & worldwide use 13,168 Menus 12,302 Windows 18,430 Dialogs & controls 25,039 Icons 9,074 Visual system 20,736 Input & behavior 14,831 Language & help 5,033 Platforms & technologies 87,705

Selected changes across the river

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 oldest surviving guide already treats observation as design work

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.”
1982 source ↗p. 11
“The primary test of the user interface is its success with users.”
1987 source ↗p. 15

1992 turns a compact desktop manual into a reference architecture

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.

User testing grows from one page into a development process

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.”
1987 source ↗p. 15
“Involve users throughout the design process and observe them working in their environment.”
1992 source ↗p. 14

Accessibility broadens into access, localization, and collaboration

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.”
1987 source ↗p. 16
“Providing universal access means creating products that all people can use, including people who have a disability.”
1992 source ↗p. 24

Icons move from interface vocabulary to a design discipline

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.”
1987 source ↗p. 10
“People often recognize pictures of things and understand them more quickly than they do verbal representations of the same things.”
1992 source ↗p. 224

One page of plain language becomes a full language-and-help system

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.”
1987 source ↗p. 14
“A good alert box message says what went wrong, why it went wrong, and what the user can do about it.”
1992 source ↗p. 311
Method & notes