THE WHOLE PRODUCT Act I · Apple II · est. 1977
  1. 1 · Apple II
  2. 2 · Lisa/Mac
  3. 3 · NeXT
  4. 4 · iMac/Cube
  5. 5 · iPod

Act I · 1977

Apple II: From Machine to Product

Central question

What changes when a machine becomes a product?

Apple II computer with beige case, keyboard and monitor, on museum display
Apple II, Smithsonian National Museum of American History. Photo: Kevin Burkett, CC BY-SA 2.0, via Wikimedia Commons.
Exhibit A · Apple II · 1977

Apple II

The promise. That a computer could be something you bought finished, plugged in and used — not something you built. The Apple I had proven the hardware worked; the Apple II had to prove it could be a product.

The object. The hardware and system software were Steve Wozniak's work, largely alone — colour graphics, expansion slots and a design far ahead of the hobbyist boards around it. Rod Holt engineered the compact switching power supply that let it run cool and quiet. Jobs pushed for a real, molded plastic enclosure instead of a bare board, designed by Jerry Manock: the case, keyboard and price tag that turned a hobbyist board into something a family could own.

The outcome. A genuine commercial success, and one that outlasted its launch year by a decade. Its trajectory changed again in 1979 with VisiCalc, the first spreadsheet program — the first piece of software people bought a computer specifically to run.

What remained. The idea that hardware, packaging and price are part of the same design problem as the circuit board — that "product" is a design discipline, not just a manufacturing step. Every later act in this museum inherits that idea, even where it disagrees about what else belongs in it.

Technical record
Released
June 1977
Design
Steve Wozniak (logic board, firmware); Rod Holt (power supply); Jerry Manock (case)
CPU
MOS 6502, 1 MHz
Memory
4 KB–48 KB RAM (model dependent)
Notable software
VisiCalc (1979), the first personal-computer spreadsheet

The Apple II proved a machine could become a product a family would buy. It did not yet ask whether that family should have to learn the machine's own logic to use it — commands, syntax, a manual. Inside Apple, a different project was starting to ask exactly that question, and it would take the company somewhere the Apple II never went.