In January 2007, Steve Jobs stood on stage and described a new product as three devices in one: a widescreen iPod, a phone, and an internet communicator. Then he said the line that stuck: these are not three separate devices, this is one device. The audience understood immediately what he meant, because the promise being made was an old one — a single object, easy enough that you didn’t think about it, that replaced a drawer full of specialized gadgets.

Jef Raskin had been making a version of that argument since the early 1980s, and he had built actual products around it. He did not live to see the iPhone. He died in February 2005, almost two years before Jobs’s keynote. But the vocabulary he spent much of his career developing — the “information appliance,” a device as unremarkable and reliable as a toaster — is close enough to what Apple promised in 2007 that the comparison is worth making carefully, without pretending Raskin ever weighed in on a product he never used.

What Raskin Meant by “Information Appliance”

Raskin did not coin the phrase “information appliance.” Versions of the term circulated in computing and consumer-electronics writing through the 1980s and 1990s, applied loosely to everything from fax machines to early internet set-top boxes. What Raskin contributed was a specific, demanding definition, developed after he left Apple in 1982 and founded a company, Information Appliance, Inc., built around it.

His standard was the household appliance: a toaster, a microwave, a telephone. You do not read a manual to use one. You do not maintain it, update it, or learn its internal model. It does a narrow job, does it reliably, and disappears into the background of daily life. Raskin argued that computers, and the software running on them, had failed to meet that standard and that the failure was a design choice, not a technical necessity.

Information Appliance, Inc. built toward the idea directly. In 1985 it released the SwyftCard, a plug-in ROM card for the Apple IIe that replaced the machine’s operating environment with Raskin’s own modeless, search-based word processor. Two years later, Information Appliance licensed the underlying technology to Canon, which manufactured and sold it as the Canon Cat — a dedicated writing appliance with no visible operating system, no file manager, and no installed applications. You turned it on and you wrote. Canon discontinued it after roughly six months amid an internal corporate reorganization, but the machine remains the clearest built example of Raskin’s appliance philosophy: not a general-purpose computer with a simpler shell, but a device engineered from the ground up to do one thing without asking anything of the user beyond that one thing.

The iPhone’s Own Appliance Framing

Apple’s 2007 pitch for the iPhone used language that would have been familiar to Raskin, even if the company was not consciously invoking him. The keynote emphasized simplicity of use over configurability: no stylus, no manual, a touch interface built to be learned by watching rather than reading. Early reviewers repeatedly reached for appliance language — describing the device as something a non-technical person could pick up and operate correctly on the first try, in a way that most 2006-era smartphones, with their stylus-driven menus and carrier-specific software, conspicuously were not.

At launch, the iPhone also fit Raskin’s definition more closely than it would for very long. There was no App Store. The phone shipped with a fixed set of Apple-built applications and no mechanism for installing more. In that narrow window, the iPhone was closer to a genuine appliance — a device with a bounded, designed-in feature set — than to the open-ended, endlessly extensible personal computer Raskin had spent his career criticizing.

Where the iPhone Still Fits the Definition

Some of Raskin’s appliance criteria held up well even as the device matured. Boot time stayed near-instant. The interface never asked a new user to understand a file system in the way a 1990s PC did; files exist, but the typical user interacts with them through applications rather than a Finder-style hierarchy. Software updates happen largely without the user’s active management. Measured against the personal computer of Raskin’s era — the machine he judged so harshly in his own writing and in his Macintosh-era memos — the iPhone clears the bar he set for basic accessibility by a wide margin.

Where It Diverges

The divergence begins with the single decision that made the iPhone what it became: the App Store, opened in July 2008. Once third-party software could be installed, the iPhone stopped being a bounded appliance and became what Raskin would have recognized as a general-purpose computer wearing an appliance’s shell. Each app is, in effect, its own small appliance with its own interface conventions, its own menus, its own way of doing the same basic tasks — the opposite of the uniform, learn-once interaction model Raskin built into the Canon Cat and argued for at length in his 2000 book, The Humane Interface.

The deeper problem, in Raskin’s own terms, is the return of modes. An app is itself a mode: the same physical gesture — a swipe, a tap on an icon that looks like a button — produces different results depending on which app currently holds the screen and what state that app is in. Raskin’s interface theory treated this kind of hidden, unpredictable state as the primary source of user error, the thing his entire career of interface work was organized around eliminating. A smartphone home screen, however cleanly designed, is a grid of separately moded environments. Notifications, background permissions, and account management add further layers of state that a toaster simply does not have and that the Canon Cat, deliberately, did not either.

There is also a narrower, more literal divergence. Raskin’s appliance ideal specialized: a writing machine, not a machine that could become anything depending on what you installed on it. The iPhone’s actual success came from the opposite move — becoming general-purpose while looking simple. That is a legitimate design achievement, but it is not the achievement Raskin was describing when he used the word “appliance.”

The Honest Limits of the Comparison

None of this is a claim that Raskin evaluated the iPhone, agreed with its design, or would have endorsed Apple’s later direction. He died two years before it existed, and nothing in his published writing addresses it. What can be said, without speculation, is that Raskin left behind a specific, well-documented standard for what an information appliance is — narrow purpose, no hidden modes, no configuration burden — and that standard is available to apply to any device, including ones he never saw.

Applied honestly, the iPhone passes on some measures and fails on others, and it fails in exactly the place Raskin cared about most: not ease of first use, but the elimination of modes. The device that made “it just works” a mass-market expectation did so by hiding complexity behind a friendly surface, not by removing it — which is precisely the distinction Raskin spent his career insisting mattered.

Frequently Asked Questions

Did Jef Raskin ever comment on the iPhone directly?

No. Raskin died on February 26, 2005, and the iPhone was announced in January 2007 and released that June. Any comparison between his information appliance principles and the iPhone is an editorial application of his documented ideas, not a report of anything Raskin said about the device.

Did Jef Raskin invent the term “information appliance”?

No. The phrase was in general use in computing and consumer-electronics writing before and alongside Raskin’s work. His contribution was a specific, demanding definition — centered on eliminating configuration and hidden modes — that he built into actual products through his company, Information Appliance, Inc.

What was the Canon Cat, and how does it relate to this idea?

The Canon Cat was a dedicated writing appliance released in 1987, built on technology licensed from Raskin’s company to Canon. It had no visible operating system or installable applications, making it the clearest built example of Raskin’s appliance philosophy before he died.

Why does Raskin’s theory treat apps as a problem rather than a feature?

Raskin’s interface theory identified “modes” — states where the same input produces different results — as a primary cause of user error. Each app functions as its own mode with its own interface conventions, which is the specific pattern his design philosophy was built to eliminate, not accommodate.

Is this article claiming the iPhone failed as a design?

No. It is a narrow, principle-by-principle comparison against a specific historical standard Raskin defined and documented. The iPhone’s commercial and usability success is not in dispute; the point is that success came through a different design path than the one Raskin’s appliance concept described.

Related:

• Information Appliances Before the Tablet: Raskin’s 1990 Idea — the same concept applied to the tablet a decade earlier
• Modes Are Still Harmful — Raskin’s core argument against hidden interface state
• The Canon Cat — Manual and Documentation — Raskin’s own built appliance
• Computer History Museum — primary materials on Information Appliance, Inc. and the Canon Cat
• Back to Ideas