Apple’s Pippin Wasn’t Too Early. It Was Too Arrogant.

You probably think Apple can do no wrong. They make trillion-dollar phones, dominate the App Store, and seem to have a Midas touch in consumer tech. But back in 1996, Apple built a gaming console. It sold exactly 42,000 units worldwide. Sony, launching around the same time, sold 100 million PlayStations. It was a humiliating, catastrophic collapse. And the reason it died has nothing to do with being “too early” and everything to do with corporate ego.

The console was called the Pippin. Apple partnered with Japanese toy giant Bandai to build it. The vision was actually brilliant: a “home multimedia system” that played games, browsed the web, and ran educational software. It was essentially the iPad, 14 years before the iPad. But when it launched, it carried a $599 price tag. A Sony PlayStation cost $299. A Nintendo 64 was $199.

Ambition must be priced in the user’s currency, not yours.

People look at that $599 price and think that was the killer. But the price was just a symptom. The real disease was Apple’s refusal to compromise. They built the Pippin using expensive Macintosh architecture and PowerPC processors because they wanted it to be a high-end platform, not a cheap toy. They invested almost no money in the project—only covering 40 engineers’ salaries while Bandai footed the rest of the bill—yet maintained a death grip on the product’s positioning. And they launched with exactly four games. Four. Sony had hundreds.

But here is the real twist, the fatal mistake that killed the Pippin faster than Sony or Nintendo ever could. Bandai had a lifeline. They wanted to market the Pippin to parents as a “learning computer.” In the 90s, devices marketed as educational tools sold like hotcakes. But Apple said no. Apple decreed that the word “computer” was strictly reserved for the Mac. Bandai was forbidden from positioning the Pippin as anything other than a gaming console.

When you protect your brand definition at the cost of your product’s survival, you don’t have a product—you have a hostage.

So the Pippin sat on store shelves, trapped in an impossible middle ground. It didn’t have the games to be a real console, and Apple wouldn’t let it be sold as the learning computer it actually was. It was an empty shell of a platform, suffering from gaming’s costs but none of gaming’s content.

When Steve Jobs returned to a dying Apple in 1997, his first move was to take the Pippin out back and shoot it. He erased it from history. He never spoke of it publicly again. But Kai-Fu Lee, who had managed the Pippin software team at Apple, chose a radically different path. Years later, Lee publicly owned the failure. He dissected the exact reasons it tanked: underfunding, fierce competition, and a complete misread of what the market actually wanted. He treated the corpse like a textbook.

Silence leaves you with regrets; autopsies leave you with wisdom.

If you are building a product right now, you are probably making the exact same mistake Apple made. You have a grand vision for a “platform” or an “ecosystem.” But users don’t care about your platform. They care about what it does for them today. Apple wanted the Pippin to be a futuristic multimedia system, but users just wanted to play games. And when Bandai found a backdoor—a way to market the device as an educational tool to get it into homes—Apple slammed the door shut to protect the Mac’s identity.

A great platform with an empty ecosystem and a forbidden alternative positioning is just an expensive lesson.

Apple eventually got the formula right with the iPad. But they only got there because they learned what happens when you build a castle and forget to build the road to it. Don’t fall in love with your own vision. Fall in love with the market’s reality. Otherwise, you’re just building another Pippin.

FAQ

Q: Wasn't the Pippin just ahead of its time?

A: No, it was ahead of its budget. The 'ahead of its time' excuse is just a coping mechanism for products that fail to solve a current, painful problem. The iPad succeeded later because the infrastructure and consumer readiness caught up, but the Pippin failed because it demanded too much money for too little immediate value.

Q: What's the practical takeaway for product builders?

A: Stop building 'platforms' and start building tools. If your grand vision doesn't have a killer use case today, your ecosystem will never exist. Let your partners position the product where it can actually survive, even if it bruises your brand ego.

Q: Why didn't Steve Jobs ever talk about the Pippin?

A: Because Jobs was a master of narrative, and the Pippin was a narrative nightmare. He preferred to erase failures rather than autopsy them in public, leaving the painful but necessary learning to people like Kai-Fu Lee who were willing to own the mess.

📎 Source: View Source