---
title: The river of Apple's interface guidelines
description: A measured, source-checked comparison of Apple's 1982, 1987, 1992, 2008, and current Human Interface Guidelines.
canonical: https://hig.josefrichter.design/
---

# The river of Apple's interface guidelines

Apple's written interface-guideline lineage begins with drafts from 1978–79 and is approaching fifty years. This river begins with the surviving 1982 Apple IIe user-interface guide, continues through published milestones in 1987 and 1992, combines the contemporary Mac OS X and first iPhone HIG into a 2008 ecosystem snapshot, and follows the same topics into today's living HIG.

The measured guidance grows from 10,975 words in 1982 to 37,314 in 1987 (3.4×), redistributing 52% of topic attention as the interface moves from keyboard-and-text interaction into a graphical desktop.

The combined 2008 bank contains 141,380 measured words across the Mac and iPhone guides; today's living HIG contains 207,459.

The HTML chart can be switched between relative scale, which compares each topic's share within an edition, and absolute scale, which uses one words-to-pixels ratio to reveal the corpus's total growth.

The historical books are not republished here. This page contains measurements, commentary, and short attributed excerpts; each source link points to an externally hosted copy.

## 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.

### 1982, page 11

> Begin your human interface design by identifying your target audience.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf)

### 1987, page 15

> The primary test of the user interface is its success with users.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

## 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.

### 1987, page 15

> The primary test of the user interface is its success with users.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

### 1992, page 14

> Involve users throughout the design process and observe them working in their environment.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

## 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.

### 1987, page 16

> Computers hold tremendous promise for people with many kinds of disabilities.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

### 1992, page 24

> Providing universal access means creating products that all people can use, including people who have a disability.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

## 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.

### 1987, page 10

> 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.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

### 1992, page 224

> People often recognize pictures of things and understand them more quickly than they do verbal representations of the same things.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

## 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.

### 1987, page 14

> Communicate with the user in concise and simple terms.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

### 1992, page 311

> A good alert box message says what went wrong, why it went wrong, and what the user can do about it.

[Open the external source](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

## Principles: 1982 → 1987 (Held)

The Apple IIe guide already treats simplicity, consistency, efficiency, learnability, memory load, anticipation, and honest feedback as interface obligations. The 1987 desktop book retains them and adds the graphical principles of metaphor, direct manipulation, see-and-point, forgiveness, and visual stability.

- **Already human-centered.** The Apple IIe guide sets goals of simplicity, consistency, efficiency, self-teaching, low memory strain, anticipation, and immediate feedback before Apple had a standard graphical desktop.
  Sources: [1982 · p. 19](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 22](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf)

- **Added graphical principles.** The 1987 book keeps familiar and predictable behavior but adds real-world metaphor, direct manipulation, see-and-point, forgiveness, perceived stability, and aesthetic integrity.
  Sources: [1982 · p. 22](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 3](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1987 · p. 8](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

This is not a jump from no design philosophy to one. The text-mode guide already argues that an interface should fit human memory, expectations, skill, and perception; the desktop edition adds principles made possible by a stable graphical object world.

In absolute terms the measured treatment grows 105%, while its corpus share falls from 19.5% to 11.8%. Held refers to continuity of intent, not a constant amount of text.

## Design process: 1982 → 1987 (Held)

The earliest bank contains a surprisingly detailed method: define audiences, write user profiles, test early, watch people directly, and revise. The 1987 book keeps the method but compresses it into a single page while moving more attention to the new desktop grammar.

- **Survived.** Both guides tell teams to identify the audience, test early with representative people, watch them directly, and revise the interface when they struggle.
  Sources: [1982 · p. 11](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 15](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 15](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Compressed.** Nine measured pages of user profiles, field observation, staged testing, and a detailed failure anecdote become a single compact testing section in 1987.
  Sources: [1982 · p. 12](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 18](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 15](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The striking reversal is editorial. User research and testing occupy a large share of the smaller 1982 guide, then shrink in the 1987 book even though the substance survives. The new graphical components consume the space instead.

In absolute terms the measured treatment shrinks 87%, while its corpus share falls from 26.3% to 1.0%. Held refers to continuity of intent, not a constant amount of text.

## Access & worldwide use: 1982 → 1987 (Arrived)

The 1982 guide adapts to novice and expert knowledge and mentions localized keyboards, but it does not treat disability access as a design field. The 1987 book introduces explicit guidance for vision, hearing, motor, and other disabilities.

- **Arrived explicitly.** The 1982 guide varies language and complexity for novice and expert audiences but contains no dedicated disability guidance; 1987 addresses vision, hearing, motor, and other disabilities directly.
  Sources: [1982 · p. 11](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 24](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 16](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Added alternate routes.** The desktop guide asks developers to preserve keyboard and other alternatives when a mouse-only action could exclude people with different physical abilities.
  Sources: [1982 · p. 25](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 18](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The earlier concern with different audiences is not the same as accessibility. In 1987, disability becomes an explicit product-design constraint and alternative access becomes something developers must plan rather than infer from general flexibility.

The quantitative view confirms the arrival: 1987 devotes 2,075 measured words, or 5.6% of its corpus, to a bank with no 1982 counterpart.

## Menus: 1982 → 1987 (Reshaped)

A menu changes from a numbered text screen whose selection is typed and confirmed with Return into a persistent graphical command system opened from the menu bar and operated by pointing, while retaining keyboard routes.

- **Changed mechanism.** The Apple IIe standard divides a text screen into title, numbered choices, and instructions; people type a number and press Return. The desktop opens pull-down command lists from a persistent menu bar.
  Sources: [1982 · p. 41](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 65](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Preserved recognition.** Both expose valid choices and retain help and keyboard access, so the move to pointing reshapes the mechanism without abandoning discoverability.
  Sources: [1982 · p. 42](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 67](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The function is continuous—show available choices instead of demanding memorized commands—but its physical grammar changes. Selection moves from typing a number or keyword on a dedicated screen to pointing at transient lists attached to a stable menu bar.

In absolute terms the measured treatment grows 1287%, while its corpus share rises from 5.5% to 22.5%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Windows: 1982 → 1987 (Arrived)

The Apple IIe guide assumes full-screen displays and sequential program states. The desktop book introduces overlapping, movable, resizable document windows as directly manipulated objects.

- **Arrived.** The earlier guide structures interaction as successive full-screen displays. The 1987 desktop introduces movable, resizable windows that frame documents and can overlap in a visible workspace.
  Sources: [1982 · p. 38](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 39](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Added spatial persistence.** Documents and tools can remain present in multiple windows, with activation and front-to-back ordering replacing the older sequence of screen changes.
  Sources: [1982 · p. 43](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 46](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

Windows are a genuinely new organizing layer in this measured lineage. They let several documents and tools remain visible, reorderable, and spatially persistent instead of replacing one full-screen state with another.

The quantitative view confirms the arrival: 1987 devotes 5,112 measured words, or 13.7% of its corpus, to a bank with no 1982 counterpart.

## Dialogs & controls: 1982 → 1987 (Reshaped)

Prompts, sequential input fields, keyword matching, and inline error messages become graphical dialogs and alerts assembled from standard buttons, fields, and selection controls.

- **Recomposed.** Sequential text prompts, typed responses, defaults, keyword completion, and inline validation become graphical dialog boxes made from visible fields, buttons, and choices.
  Sources: [1982 · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 35](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 55](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Preserved recovery.** Both eras require errors to identify the problem and point toward a solution, but the desktop adds standardized alerts and explicit confirmation controls.
  Sources: [1982 · p. 37](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 59](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The older interaction is conversational and serial: prompt, type, validate, advance. The graphical dialog makes choices visible together and lets standard controls communicate both the available value and the method of changing it.

In absolute terms the measured treatment grows 34%, while its corpus share falls from 21.6% to 8.5%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Icons: 1982 → 1987 (Arrived)

The text interface communicates through words, numbers, cursor shapes, inverse video, and flashing. The 1987 desktop adds icons as persistent graphical objects and command targets.

- **Arrived.** The text interface distinguishes states through cursor shapes, characters, inverse video, and flashing; it has no persistent graphical object vocabulary.
  Sources: [1982 · p. 25](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 38](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf)

- **Made objects visible.** The desktop represents disks, documents, folders, and tools as recognizable pictures that people can select and manipulate directly.
  Sources: [1987 · p. 9](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1987 · p. 20](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

Cursor shape and text styling carry state in 1982, but they do not form an object vocabulary. Icons arrive with the desktop metaphor, giving files, folders, disks, and tools visible identities that can be selected and manipulated.

The quantitative view confirms the arrival: 1987 devotes 1,083 measured words, or 2.9% of its corpus, to a bank with no 1982 counterpart.

## Visual system: 1982 → 1987 (Reshaped)

Visual guidance moves from managing inverse video, flashing, focus, and television-display limits in 40- or 80-column text to composing a graphical screen with pictures, spatial hierarchy, and restrained color.

- **Escaped text mode.** The Apple IIe guide concentrates on whether inverse video, flashing, focus, and column layouts remain legible across televisions and monitors.
  Sources: [1982 · p. 38](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Added graphical composition.** The desktop guide can now discuss pictures, spatial grouping, screen balance, visual consistency, and restrained color as a coherent graphic system.
  Sources: [1982 · p. 38](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 33](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The constraint shifts from whether text effects survive heterogeneous televisions and monitors to how graphics establish hierarchy without clutter. The later visual bank is broader because the display can now represent objects, depth, and color rather than characters alone.

In absolute terms the measured treatment grows 660%, while its corpus share rises from 2.8% to 6.3%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Input & behavior: 1982 → 1987 (Reshaped)

The 1982 interaction grammar is built from cursor shapes, arrow keys, Return, Escape, control characters, typed commands, and immediate keyboard feedback. By 1987, the one-button mouse and direct pointing share that role with the keyboard.

- **Preserved keyboard grammar.** Arrow keys, Return, Escape, deletion, defaults, shortcuts, and visible input feedback remain useful conventions in the later system.
  Sources: [1982 · p. 26](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 28](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 93](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Added pointing.** The 1987 guide makes a one-button mouse the standard pointing device and adds click, drag, selection, and direct manipulation to the typed-command model.
  Sources: [1982 · p. 30](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 28](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1987 · p. 94](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The keyboard does not disappear; many of its escape, confirmation, editing, and shortcut conventions survive. What changes is that pointing makes location and objects part of the command, reducing dependence on typed identifiers and sequential prompts.

In absolute terms the measured treatment grows 434%, while its corpus share rises from 17.2% to 27.1%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Language & help: 1982 → 1987 (Held)

Both guides insist on familiar vocabulary, clear errors, consistent key names, discoverable help, and visible status. The later book generalizes those rules from text prompts into the graphical interface.

- **Survived.** Both books require familiar words, consistent terminology, clear error messages, visible status during delays, and help that returns people safely to their work.
  Sources: [1982 · p. 37](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 40](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1982 · p. 43](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

- **Changed surface.** Language moves from prompts and dedicated help screens into menus, dialogs, alerts, icons, and other parts of the graphical interface.
  Sources: [1982 · p. 40](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1982%20Apple%20IIe%20Design%20Guidelines.pdf) · [1987 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf)

The continuity is unusually direct: say what happened, show what can be done, use the names people see on the hardware, and keep help recoverable. Graphics expand the surfaces carrying those words but do not replace their communicative job.

In absolute terms the measured treatment shrinks 64%, while its corpus share falls from 7.1% to 0.7%. Held refers to continuity of intent, not a constant amount of text.

## Principles: 1987 → 1992 (Held)

The core philosophy holds, but it becomes more concentrated. Consistency, user control, familiar metaphors, direct manipulation, and forgiveness remain the foundation while more applied guidance moves into dedicated chapters.

- **Survived.** Real-world metaphors, direct manipulation, see-and-point, consistency, user control, feedback, and forgiveness remain the core grammar.
  Sources: [1987 · p. 3](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 4](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** The 1992 edition names perceived stability, modelessness, and aesthetic integrity as principles in their own right, making calmness and visual coherence explicit design obligations.
  Sources: [1987 · p. 8](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 12](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

What changes is where the philosophy lives. In 1987, principles are interleaved with the explanation of the desktop model; by 1992 they work more like an opening constitution, while menus, windows, controls, icons, and language carry the operational detail in chapters of their own.

In absolute terms the measured treatment shrinks 15%, while its corpus share falls from 11.8% to 5.0%. Held refers to continuity of intent, not a constant amount of text.

## Design process: 1987 → 1992 (Expanded)

A one-page insistence that users determine an interface's success becomes a sixteen-page design-and-development process: define the audience and tasks, prototype, observe people using the product, and iterate.

- **Made procedural.** The 1987 book already asks for early paper tests, representative participants, think-aloud observation, and repeated revision; 1992 turns those ideas into named steps: define the audience, analyze tasks, build prototypes, observe, revise, and test again.
  Sources: [1987 · p. 15](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 41](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Made stricter.** The later protocol tells observers not to rescue struggling participants and to treat mistakes as evidence of faulty product design, not participant failure.
  Sources: [1987 · p. 15](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 44](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

The important change is procedural, not merely editorial. Testing stops being a final test of whether the interface succeeded and becomes a repeated activity inside design: identify people and tasks, build representations early, observe use, and feed the result back into the next iteration.

In absolute terms the measured treatment grows 1124%, while its corpus share rises from 1.0% to 6.1%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Access & worldwide use: 1987 → 1992 (Expanded)

The disability guidance survives and broadens into universal access. The 1992 treatment places it beside worldwide compatibility and collaboration, turning access from a special case into a general product concern.

- **Broadened.** Guidance framed in 1987 as designing for disabled people becomes a principle that the computer should be accessible to everyone, including people with physical, cognitive, linguistic, age, and ability differences.
  Sources: [1987 · p. 16](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** Worldwide compatibility becomes concrete interface work: multiple script systems, right-to-left layouts, localized keyboards, and room for translated menu titles and dialog text.
  Sources: [1987 · p. 17](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 22](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

The later book treats access as something mainstream products must plan for rather than an optional adaptation. It also connects disability access with internationalization and networked work, widening the implied user from an individual at one Macintosh to people with different bodies, languages, locales, and collaborators.

In absolute terms the measured treatment grows 109%, while its corpus share rises from 5.6% to 5.8%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Menus: 1987 → 1992 (Expanded)

Menu behavior was already one of the largest parts of the 1987 book. In 1992 it becomes an eighty-two-page reference chapter with a more systematic account of menu anatomy, command wording, states, keyboard equivalents, and menu families.

- **Survived.** The durable syntax is already present in 1987: frequent commands near the top, Quit near the bottom, unavailable items dimmed, keyboard equivalents, and an ellipsis only when more information is required.
  Sources: [1987 · p. 67](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 60](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** The 1992 book adds distinct rules for scrolling, hierarchical, pop-up, tear-off, and palette menus instead of treating the pull-down menu as nearly the whole system.
  Sources: [1987 · p. 65](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 73](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

The 1987 rules already define much of the durable menu grammar. The 1992 edition turns that grammar into a lookup system: designers can find separate guidance for command names, grouping, enabling and disabling, keyboard equivalents, hierarchical menus, and the standard menus expected across applications.

In absolute terms the measured treatment grows 83%, while its corpus share falls from 22.5% to 20.7%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Windows: 1987 → 1992 (Held)

The desktop window model remains recognizable: opening, closing, moving, resizing, scrolling, and managing multiple windows. The 1992 book elaborates the same model rather than replacing it.

- **Survived.** The window remains a directly manipulated object with a title bar, close and zoom controls, resizing, scrolling, activation, and front-to-back ordering.
  Sources: [1987 · p. 39](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 133](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Clarified.** The later book distinguishes document windows and utility windows and specifies how active, inactive, modal, and modeless windows relate, rather than leaving most of that behavior implicit.
  Sources: [1987 · p. 55](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 131](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

This is continuity through elaboration. The object and its direct-manipulation behaviors remain stable, while the later edition makes edge cases and relationships—activation, ordering, zooming, scrolling, document windows, utility windows, and multiple-window behavior—more explicit.

In absolute terms the measured treatment grows 65%, while its corpus share falls from 13.7% to 11.4%. Held refers to continuity of intent, not a constant amount of text.

## Dialogs & controls: 1987 → 1992 (Expanded)

A compact treatment of dialogs and alerts expands into a full controls vocabulary. The later book separates alert behavior, modal interaction, buttons, fields, lists, sliders, and other controls into explicit reusable rules.

- **Survived.** A menu ellipsis still promises that a dialog will gather information before the command runs; defaults should be prefilled and the likely action should respond to Return.
  Sources: [1987 · p. 58](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 176](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** The 1992 edition separates movable modal, application-modal, and modeless dialogs and requires modeless dialogs to coexist with access to valid windows and menu commands.
  Sources: [1987 · p. 58](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 181](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

Dialogs cease to be treated mainly as exceptional interruptions. They become containers for a systematic control language, with clearer distinctions between alerts, modal and modeless interaction, command buttons, text entry, selection controls, and feedback.

In absolute terms the measured treatment grows 304%, while its corpus share rises from 8.5% to 17.2%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Icons: 1987 → 1992 (Expanded)

Icons move from one element of graphic communication and the desktop metaphor to a design discipline of their own, covering recognition, metaphor choice, cultural limits, families, sizes, bit depth, and testing.

- **Expanded.** A brief instruction to make desktop objects look like what they do becomes a full method for building recognizable icon families across sizes, states, color depths, and masks.
  Sources: [1987 · p. 9](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 223](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** The later book warns that office metaphors, humor, code names, and symbols may not travel across cultures, so icon recognition has to be tested worldwide rather than assumed.
  Sources: [1987 · p. 10](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 227](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

The later chapter treats an icon as a designed family rather than an isolated small picture. Recognition, metaphor, cultural interpretation, consistency across states and sizes, technical production limits, and testing all become part of the same design problem.

In absolute terms the measured treatment grows 536%, while its corpus share rises from 2.9% to 9.3%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Visual system: 1987 → 1992 (Reshaped)

The visual concern changes shape. The 1987 book combines screen design and graphic communication; 1992 moves icon design into its own large chapter and leaves a shorter, more specifically color-oriented visual treatment.

- **Survived.** Both editions warn that color must not carry meaning by itself and that standard interface chrome should remain restrained so content, not decoration, attracts attention.
  Sources: [1987 · p. 33](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 257](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Narrowed.** The 1992 visual chapter concentrates on color behavior—palettes, contrast, pointers, and display limits—because icon construction has moved into its own much larger chapter.
  Sources: [1987 · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 260](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

This bank becomes smaller partly because its former responsibilities split apart. Iconography graduates into a large independent discipline, while the remaining visual chapter concentrates more narrowly on color and display conditions. The concern persists, but its boundaries are redrawn.

In absolute terms the measured treatment shrinks 8%, while its corpus share falls from 6.3% to 2.9%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Input & behavior: 1987 → 1992 (Held)

Keyboard and mouse behavior remain the interaction backbone. The later edition adds resolution and examples, but the underlying model of pointing, selecting, dragging, typing, and keyboard equivalents stays stable.

- **Survived.** Both books make the one-button mouse the standard pointing device and say that merely moving it should move only the pointer; visible content changes begin with a button action.
  Sources: [1987 · p. 28](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 269](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Made inclusive.** The 1992 edition states that double-clicking is only a shortcut and must never be the sole route to an action because some novices, children, and people with disabilities may not be able to perform it reliably.
  Sources: [1987 · p. 93](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 272](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

Both books assume the same primary instruments and preserve the same interaction grammar: point, click, select, drag, type, and provide keyboard access to commands. The later book clarifies behaviors and conventions without introducing a new input paradigm.

In absolute terms the measured treatment stays nearly level, while its corpus share falls from 27.1% to 14.0%. Held refers to continuity of intent, not a constant amount of text.

## Language & help: 1987 → 1992 (Expanded)

One page instructing designers to write directly and plainly becomes a twenty-four-page language-and-help system spanning terminology, tone, alerts, documentation, interactive help, and Balloon Help.

- **Expanded.** The 1987 rule to communicate in concise, simple language becomes guidance for consistent terminology across menus, dialogs, alerts, documentation, and help.
  Sources: [1987 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 305](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

- **Added.** Balloon Help makes explanation part of the live interface: every difficult control can reveal a short, context-specific description instead of sending people to a separate manual.
  Sources: [1987 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1987%20Apple%20Human%20Interface%20Guidelines%20-%20The%20Apple%20Desktop%20Interface.pdf) · [1992 · p. 318](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf)

The expansion makes writing part of interface architecture. Terminology must stay consistent across menus, dialogs, alerts, documentation, and help; messages must explain both the problem and the available recovery; and help becomes an interactive layer rather than a separate manual alone.

In absolute terms the measured treatment grows 1916%, while its corpus share rises from 0.7% to 7.5%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Principles: 1992 → 2008 (Held)

The classic Macintosh principles remain almost intact in the 2008 Mac guide, while the first iPhone guide distills them to metaphor, direct manipulation, see-and-point, feedback, user control, and aesthetic integrity.

- **Survived on Mac.** WYSIWYG, modelessness, direct manipulation, feedback, user control, forgiveness, and aesthetic integrity remain a named Mac design constitution.
  Sources: [1992 · p. 9](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 39](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Distilled for iPhone.** The first iPhone guide keeps metaphor, direct manipulation, see-and-point, feedback, user control, and aesthetic integrity, but drops principles tied to a persistent desktop.
  Sources: [1992 · p. 4](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

The apparent continuity hides an important split. Mac keeps nearly the full 1992 constitution; iPhone keeps only the principles that transfer cleanly to a small direct-touch device.

In absolute terms the measured treatment grows 265%, while its corpus share rises from 5.0% to 9.6%. Held refers to continuity of intent, not a constant amount of text.

## Design process: 1992 → 2008 (Held)

The desktop guide preserves task analysis, prototyping, and user observation. The iPhone guide adds a product-definition statement and an explicit discipline of focusing the application on one primary task.

- **Survived.** The Mac guide retains audience and task analysis, prototypes, observation, iteration, and the instruction to treat participant mistakes as evidence about the design.
  Sources: [1992 · p. 41](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 25](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Added product definition.** The iPhone guide asks teams to state the product's audience and purpose, then focus the application on a primary task instead of reproducing a desktop feature list.
  Sources: [iPhone OS · p. 35](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 39](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

User observation remains an explicit development activity, but the iPhone branch adds product strategy: decide what the product is for, strip away secondary features, and build around the primary task.

In absolute terms the measured treatment stays nearly level, while its corpus share falls from 6.1% to 3.2%. Held refers to continuity of intent, not a constant amount of text.

## Access & worldwide use: 1992 → 2008 (Held)

Worldwide compatibility and universal access remain explicit in the Mac guide. The first iPhone HIG has no dedicated accessibility chapter, so the concern is carried by only one branch of the 2008 snapshot.

- **Survived on Mac.** Universal access and worldwide compatibility remain explicit Mac design work, including assistive technologies, localization, scripts, and culturally portable imagery.
  Sources: [1992 · p. 14](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 47](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Missing on iPhone.** The first iPhone HIG has no dedicated accessibility bank; the 2008 snapshot carries the concern through the Mac branch alone.
  Sources: [Mac OS X · p. 47](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

This is continuity with an uneven platform boundary. The Mac book carries accessibility forward; the first iPhone book concentrates on the new device model and leaves accessibility implicit.

In absolute terms the measured treatment shrinks 49%, while its corpus share falls from 5.8% to 1.6%. Held refers to continuity of intent, not a constant amount of text.

## Menus: 1992 → 2008 (Held)

The Mac branch preserves the menu bar and adds contextual and Dock menus. The iPhone branch contains no menu chapter at all; commands move into navigation bars, toolbars, tab bars, and direct onscreen controls.

- **Expanded on Mac.** The menu bar survives alongside contextual menus and Dock menus, with the old command grammar and ellipsis convention still recognizable.
  Sources: [1992 · p. 52](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 161](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 184](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Replaced on iPhone.** The iPhone guide has no menu chapter; navigation bars, tab bars, toolbars, and direct controls distribute the commands across the screen.
  Sources: [iPhone OS · p. 61](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 68](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

Menu grammar survives unchanged on Mac but is not the organizing model on iPhone. The same need to expose commands is solved through persistent bars and directly visible controls instead.

In absolute terms the measured treatment shrinks 46%, while its corpus share falls from 20.7% to 5.9%. Held refers to continuity of intent, not a constant amount of text.

## Windows: 1992 → 2008 (Reshaped)

Aqua elaborates desktop windows with toolbars, source lists, sheets, drawers, and inspectors. The iPhone guide makes the opposite constraint explicit: one screen and one application at a time.

- **Elaborated on Mac.** Aqua adds toolbars, source lists, sheets, drawers, inspectors, and new window appearances to the inherited document-window model.
  Sources: [1992 · p. 131](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 187](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 229](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Reversed on iPhone.** The first iPhone model is deliberately single-tasking: one application at a time and one screen at a time replace the overlapping desktop workspace.
  Sources: [iPhone OS · p. 16](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 55](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

The two books now disagree productively about the basic container. Mac adds richer window types; iPhone treats a full device screen and a navigation stack as the default unit of experience.

In absolute terms the measured treatment grows 94%, while its corpus share rises from 11.4% to 11.6%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Dialogs & controls: 1992 → 2008 (Expanded)

The desktop control vocabulary grows dramatically, while iPhone recasts modal choices as alerts, action sheets, and full-screen modal views designed for touch.

- **Expanded on Mac.** The Mac guide turns the control chapter into a large component reference spanning dialogs, buttons, fields, lists, tables, selectors, indicators, and layout behavior.
  Sources: [1992 · p. 175](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 230](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 336](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Recast for touch.** iPhone uses alerts, action sheets, modal views, table views, and touch-sized controls instead of desktop dialog boxes.
  Sources: [iPhone OS · p. 69](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 104](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

The desktop branch grows by enumeration, while iPhone compresses the vocabulary into a few touch-first presentations. Both still distinguish informing, choosing, and collecting input.

In absolute terms the measured treatment grows 228%, while its corpus share rises from 17.2% to 29.7%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Icons: 1992 → 2008 (Reshaped)

One bitmap icon family becomes two identity systems: high-resolution Aqua application and document icons on Mac, and separate app, Settings, toolbar, tab-bar, and launch imagery on iPhone.

- **Rebuilt for Aqua.** Mac icon families become high-resolution, perspective-rich application, document, toolbar, and preference imagery rather than small bitmap sets for display depths.
  Sources: [1992 · p. 231](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 135](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Split on iPhone.** The iPhone guide separates app and Settings icons from toolbar, tab-bar, navigation, and launch imagery, each with a different system role.
  Sources: [iPhone OS · p. 105](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 116](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

Icon design stops being one technical family. The platform and placement now determine format, scale, silhouette, detail, and whether the image identifies an app or performs an action.

In absolute terms the measured treatment grows 42%, while its corpus share falls from 9.3% to 6.9%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Visual system: 1992 → 2008 (Expanded)

The black-and-white-first Macintosh system gives way to Aqua's color, transparency, animation, and spatial polish, while iPhone adds a compact branded screen with tightly controlled system chrome.

- **Reversed on Mac.** The black-and-white-first rule yields to Aqua's color, transparency, animation, depth, and highly polished controls.
  Sources: [1992 · p. 257](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 19](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 337](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Constrained on iPhone.** The iPhone guide allows branding and custom visual expression but asks it to coexist with familiar system chrome and a focused task.
  Sources: [iPhone OS · p. 43](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 44](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

Visual guidance changes from surviving display limits to constructing a branded platform experience. Depth, polish, translucency, and animation become intended qualities rather than constraints to avoid.

In absolute terms the measured treatment grows 83%, while its corpus share stays near 2.9%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Input & behavior: 1992 → 2008 (Reshaped)

Mouse and keyboard behavior survives on Mac, but Multi-Touch creates a second interaction grammar built around tapping, flicking, pinching, rotation, and targets large enough for fingers.

- **Preserved on Mac.** Mouse and keyboard remain the Mac interaction backbone, including pointing, selection, dragging, keyboard focus, and command equivalents.
  Sources: [1992 · p. 268](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 95](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Added direct touch.** Multi-Touch introduces tapping, flicking, pinching, and rotation, while finger-sized targets acknowledge that a finger is larger and less precise than a mouse pointer.
  Sources: [iPhone OS · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 41](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

For the first time the corpus has two primary physical grammars at once. The behavioral goals remain, but precision, target size, feedback, and discoverability must be reconsidered for fingers.

In absolute terms the measured treatment grows 49%, while its corpus share falls from 14.0% to 11.0%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Language & help: 1992 → 2008 (Reshaped)

Balloon Help disappears. Mac uses Apple Help and hover help tags; iPhone argues for minimal help and makes concise communication part of keeping the product focused.

- **Replaced on Mac.** Balloon Help gives way to Apple Help and short help tags attached to controls whose purpose is not immediately clear.
  Sources: [1992 · p. 318](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 80](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 125](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Minimized on iPhone.** The iPhone guide tells applications to communicate clearly and minimize the need for separate help by keeping the product focused and understandable.
  Sources: [iPhone OS · p. 17](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 40](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

Help changes from a universal overlay into a platform choice: searchable documentation on Mac, and a deliberate attempt to make iPhone software need almost no help at all.

In absolute terms the measured treatment shrinks 27%, while its corpus share falls from 7.5% to 2.9%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Platforms & technologies: 1992 → 2008 (Arrived)

Platform guidance arrives as a substantial body of its own: Mac OS X technologies, installation, security, and system services sit beside an entirely new iPhone OS product and application model.

- **Arrived on Mac.** System technologies, security, installation, preferences, services, printing, and application packaging become a substantial design bank of their own.
  Sources: [1992 · p. 3](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/1992%20Macintosh%20Human%20Interface%20Guidelines.pdf) · [Mac OS X · p. 59](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf)

- **Forked into mobile.** A second guide now defines an entire iPhone OS application model: touch, small screens, device capabilities, system integration, and common mobile tasks.
  Sources: [iPhone OS · p. 11](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 45](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf)

This is the point where platform constraints become first-class editorial material. The guidelines explain not just interface elements but the environment, services, lifecycle, and product shape around them.

The quantitative view confirms the arrival: 2008 devotes 21,119 measured words, or 14.9% of its corpus, to a bank with no 1992 counterpart.

## Principles: 2008 → Today (Held)

Agency, feedback, familiarity, and forgiveness persist, but today's principles add explicit responsibility for privacy, inclusion, varied input methods, platform intent, craft, and delight.

- **Survived.** User control, feedback, familiarity, forgiveness, and aesthetic integrity remain visible even though the living HIG reorganizes and renames them.
  Sources: [Mac OS X · p. 39](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 31](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · design principles](https://developer.apple.com/design/human-interface-guidelines/design-principles)

- **Added responsibility.** Today's principles explicitly add privacy, inclusion, varied input methods, platform intent, craft, and delight to the older interaction constitution.
  Sources: [iPhone OS · p. 33](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · design principles](https://developer.apple.com/design/human-interface-guidelines/design-principles)

The modern principles page recombines the shared intent of both 2008 branches and adds obligations created by connected, data-rich, adaptive, and AI-enabled products.

In absolute terms the measured treatment shrinks 92%, while its corpus share falls from 9.6% to 0.5%. Held refers to continuity of intent, not a constant amount of text.

## Design process: 2008 → Today (Dissolved)

The 2008 Mac guide still teaches a complete user-centered design method, and the iPhone guide teaches product definition. Neither has a direct counterpart in today's outcome-oriented HIG.

- **Left out.** The 2008 Mac guide still teaches task analysis, prototypes, observation, iteration, and testing; today's HIG has no comparable end-to-end method chapter.
  Sources: [Mac OS X · p. 25](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · getting started](https://developer.apple.com/design/human-interface-guidelines/getting-started)

- **Left out too.** The first iPhone guide's product-definition statement and primary-task exercise also disappear as formal steps, surviving only as scattered outcome-oriented advice.
  Sources: [iPhone OS · p. 35](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · design principles](https://developer.apple.com/design/human-interface-guidelines/design-principles)

This remains a corpus-boundary change, now dated more precisely: Apple still published a full research and prototyping method in 2008, but the living HIG no longer acts as a development-process manual.

The measured bank falls from 4,463 words and 3.2% of 2008 to no direct Today counterpart. Dissolved describes where the material lives in this corpus, not whether the practice still exists.

## Access & worldwide use: 2008 → Today (Expanded)

A short, Mac-only universal-access section becomes cross-platform guidance for vision, hearing, mobility, cognition, VoiceOver, Dynamic Type, captions, contrast, haptics, and inclusive representation.

- **Crossed platforms.** A short Mac-only universal-access section becomes a core concern across every platform rather than a compatibility note attached to desktop software.
  Sources: [Mac OS X · p. 47](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)

- **Became measurable.** Current guidance names VoiceOver, Dynamic Type, captions, contrast, haptics, keyboard access, motion settings, and concrete outcomes designers can test.
  Sources: [Mac OS X · p. 49](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)

Access becomes a cross-cutting product quality backed by named system technologies and testable outcomes, rather than a short compatibility section attached primarily to desktop software.

In absolute terms the measured treatment grows 500%, while its corpus share rises from 1.6% to 6.3%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Menus: 2008 → Today (Held)

Menus were still desktop-specific in 2008. They now span Mac menu bars, touch and edit menus, contextual actions, Home Screen quick actions, app shortcuts, and spatial presentations.

- **Crossed into touch.** The first iPhone guide omitted menus; current guidance brings them to touch through edit menus, contextual menus, Home Screen actions, and app shortcuts.
  Sources: [iPhone OS · p. 61](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · menus](https://developer.apple.com/design/human-interface-guidelines/menus)

- **Survived on Mac.** The desktop menu bar and its command semantics remain, including the distinction between an immediate action and a command that needs more information.
  Sources: [Mac OS X · p. 161](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · the menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar)

The command model crosses the platform boundary. Touch no longer means menus are absent; menus adapt their position, density, imagery, and invocation to each input method.

In absolute terms the measured treatment grows 47%, while its corpus share stays near 5.9%. Held refers to continuity of intent, not a constant amount of text.

## Windows: 2008 → Today (Reshaped)

The iPhone rules that assumed one application and one screen at a time are reversed by multitasking, multiple scenes, iPad windows, tabs, and spatial windows, while the Aqua desktop lineage remains recognizable.

- **Reversed on mobile.** The one-application, one-screen iPhone model gives way to multiple scenes, iPad multitasking, tabbed workspaces, and windowed mobile apps.
  Sources: [iPhone OS · p. 16](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · windows](https://developer.apple.com/design/human-interface-guidelines/windows)

- **Escaped the display.** The Aqua window lineage persists, while visionOS turns a window into a plane placed in physical space and adds volumetric content.
  Sources: [Mac OS X · p. 187](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · designing for visionos](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos)

The old fork begins to rejoin: desktop windows persist, while mobile gains scenes, multitasking, split views, and windows of its own; spatial computing then makes the window a plane in physical space.

In absolute terms the measured treatment grows 12%, while its corpus share falls from 11.6% to 8.9%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Dialogs & controls: 2008 → Today (Held)

Alerts, action sheets, modality, buttons, pickers, and fields remain, but the system now selects among platform-specific presentations and strongly favors undo or inline feedback over interruption.

- **Survived.** Alerts, action sheets, modality, buttons, fields, pickers, and selection controls remain recognizable components across the ecosystem.
  Sources: [iPhone OS · p. 69](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets) · [current · modality](https://developer.apple.com/design/human-interface-guidelines/modality)

- **Interrupted less.** Modern alerts are reserved for essential actionable information, and routine destructive actions should often be recoverable with undo instead of a warning.
  Sources: [Mac OS X · p. 230](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)

The vocabulary is recognizable, but interruption is treated more cautiously and each platform can choose a different component for the same decision or short task.

In absolute terms the measured treatment shrinks 40%, while its corpus share falls from 29.7% to 12.1%. Held refers to continuity of intent, not a constant amount of text.

## Icons: 2008 → Today (Reshaped)

Hand-built Aqua and iPhone image families give way to scalable SF Symbols, system masking and effects, appearance variants, and a clearer separation between interface symbols and app identity.

- **Systematized.** Hand-built interface icon families give way to SF Symbols that scale across weights, sizes, rendering modes, and platform contexts.
  Sources: [Mac OS X · p. 135](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 105](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · sf symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)

- **Separated from identity.** App icons remain bespoke identity artwork, but the system now masks, layers, and adapts them across appearances instead of requiring every rendition by hand.
  Sources: [iPhone OS · p. 105](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · app icons](https://developer.apple.com/design/human-interface-guidelines/app-icons)

The production burden moves from drawing every rendition to choosing semantic symbols and supplying identity artwork that the system can adapt across contexts.

In absolute terms the measured treatment shrinks 7%, while its corpus share falls from 6.9% to 4.4%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Visual system: 2008 → Today (Expanded)

Aqua and the first iPhone UI define fixed platform looks. Today's visual system adapts through semantic color, Dark Mode, materials, motion settings, Dynamic Type, haptics, wide gamut, and spatial depth.

- **Made adaptive.** The fixed Aqua and early iPhone looks become a semantic visual system that responds to Dark Mode, text size, contrast, motion settings, gamut, and materials.
  Sources: [Mac OS X · p. 337](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 43](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · dark mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode)

- **Added spatial depth.** Visual hierarchy now includes translucent materials, environmental lighting, motion, haptics, and spatial depth rather than targeting one flat display style.
  Sources: [Mac OS X · p. 19](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · color](https://developer.apple.com/design/human-interface-guidelines/color) · [current · designing for visionos](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos)

The visual system becomes responsive to user settings, device capabilities, environment, and depth. A platform no longer has one fixed appearance to reproduce.

In absolute terms the measured treatment grows 428%, while its corpus share rises from 2.8% to 10.0%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.

## Input & behavior: 2008 → Today (Reshaped)

The 2008 split between mouse-and-keyboard and Multi-Touch expands into one multimodal system spanning touch, pointer, keys, remote, game controller, Pencil, voice, gaze, and Digital Crown.

- **Unified modalities.** Separate Mac mouse-and-keyboard and iPhone touch grammars become shared concepts expressed through touch, pointer, keys, remote, controller, Pencil, voice, gaze, and Digital Crown.
  Sources: [Mac OS X · p. 95](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 41](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · focus and selection](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection)

- **Made pre-activation useful.** Hover, focus, and gaze can now preview or highlight before activation, reversing the older assumption that pointer movement alone should change only the pointer.
  Sources: [Mac OS X · p. 95](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [current · focus and selection](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection) · [current · apple pencil and scribble](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble)

Mouse and touch are no longer separate editorial worlds. Modern guidance defines shared concepts such as focus, selection, activation, and feedback, then explains how each modality expresses them.

In absolute terms the measured treatment stays nearly level, while its corpus share falls from 11.0% to 7.1%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Language & help: 2008 → Today (Reshaped)

Apple Help, help tags, and the iPhone principle of minimal help are redistributed across onboarding, writing, launching, loading, feedback, recovery, and contextual assistance.

- **Redistributed.** Apple Help, help tags, and the iPhone principle of minimal help are now spread across onboarding, inline guidance, feedback, recovery, and task-specific assistance.
  Sources: [Mac OS X · p. 80](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 17](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · offering help](https://developer.apple.com/design/human-interface-guidelines/offering-help)

- **Moved into the journey.** Modern guidance organizes explanation around first run, waiting, errors, and contextual moments rather than around one documentation technology.
  Sources: [iPhone OS · p. 40](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding) · [current · alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)

The modern organization follows moments in the product journey instead of a documentation technology: first run, waiting, feedback, failure, recovery, and contextual help.

In absolute terms the measured treatment grows 23%, while its corpus share falls from 2.9% to 2.4%. Reshaped identifies the change in mechanisms and organization rather than volume alone.

## Platforms & technologies: 2008 → Today (Expanded)

Two platform books become one continuously revised ecosystem corpus covering six platforms plus system experiences, services, capabilities, machine learning, and generative AI.

- **Became an ecosystem.** Two platform books become one continuously revised corpus for six platforms plus shared services, system experiences, and capabilities.
  Sources: [Mac OS X · p. 59](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-06%20Apple%20Human%20Interface%20Guidelines.pdf) · [iPhone OS · p. 11](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · technologies](https://developer.apple.com/design/human-interface-guidelines/technologies)

- **Added new canvases and risks.** Spatial computing and generative AI add gaze-and-hand interaction, 3D presentation, model uncertainty, provenance, privacy, and permission before irreversible actions.
  Sources: [iPhone OS · p. 11](https://github.com/gingerbeardman/apple-human-interface-guidelines/blob/main/2008-11%20iPhone%20Human%20Interface%20Guidelines.pdf) · [current · designing for visionos](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos) · [current · generative ai](https://developer.apple.com/design/human-interface-guidelines/generative-ai)

The 2008 fork becomes an ecosystem. Much of the corpus's later growth comes from platform- and technology-specific guidance rather than longer treatment of the original desktop components.

In absolute terms the measured treatment grows 315%, while its corpus share rises from 14.9% to 42.3%. Expanded refers to richer dedicated treatment, even when the rest of the corpus is growing too.