The night Nintendo dumped Sony on stage — and accidentally built the PlayStation.
A true story about platforms, partnerships, and what happens when the company you were building for decides to build without you.
The setup (1988–1991)
The Super Nintendo (SNES) shipped games on cartridges. Cartridges were fast but tiny and expensive to manufacture. Meanwhile a new format was eating the world: the compact disc. CDs held roughly 450× more data than an SNES cartridge and were cheap to stamp.
Nintendo wanted a CD add-on but didn't have the disc engineering chops. So they teamed up with Sony — then mostly known for Walkmans and TVs — to co-develop a CD drive for the SNES. An engineer named Ken Kutaragi led Sony's side. The device even had a working name: Play Station.
The betrayal (CES, June 1991)
On May 28, 1991, Sony announced at the Consumer Electronics Show in Chicago that the Sony–Nintendo "Play Station" was real. It was Sony's biggest moment in gaming ever.
The very next morning, Nintendo took the same stage and announced they were partnering with Philips — a European rival — to build the CD add-on instead. Sony's execs found out at the same time as the audience. No phone call. No warning. Just a public flip.
Nintendo's read: the contract Sony had negotiated gave Sony too much control over CD games. Rather than renegotiate privately, Nintendo blew the whole thing up on stage.
The consequence (1994 →)
Sony's chairman was humiliated. Ken Kutaragi convinced him to keep going — alone. Three years later, Sony launched the PlayStation. It sold over 100 million units, pulled developers like Square (Final Fantasy VII) away from Nintendo forever, and turned Sony into the dominant console maker for two decades.
The Nintendo–Philips CD add-on? Cancelled. All Nintendo got out of the deal was a handful of famously terrible Zelda and Mario games on the Philips CD-i.
Why this story lives in our library
Every game you build in a Lovable app rides on top of someone else's platform — Lovable itself, the model providers behind it, the browser, the OS. Platforms are gravity. When you understand who owns the platform, you understand who owns your future.
The Sony/Nintendo story is the cleanest example in gaming history of a platform partnership going sideways — and the "loser" becoming bigger than the "winner." Good thing to think about before you build.
Is a Lovable app a console, or a game engine?
You asked whether it makes sense to think of a Lovable app like BlockCraft Unlimited or Old School Revival as a "console" that students then build games on top of. Here's the honest answer:
A console is a finished product a player picks up. It has a look, a name, a vibe, and a library of games. "I built a game for the BlockCraft console" is a great sentence for a 10-year-old to say at the dinner table. It also captures the emotional truth: the students are picking a home for their creation.
Where it strains: real consoles are closed hardware. Your students aren't shipping cartridges — they're remixing the source. So "console" oversells the boundary.
Engines (Unity, Unreal, Godot, Roblox) are toolkits — you get physics, rendering, an entity system, and a project template, and you build inside them. That's much closer to what BlockCraft Unlimited and Old School Revival actually are: opinionated starter worlds with mechanics, art, and hooks already wired up.
Where it strains: engines are usually invisible to the end player. Your platforms are also playable on their own, which engines aren't.
Use "platform" as the umbrella word, and let students pick the metaphor that fires them up. For pitching to parents and peers: console. For explaining the actual work: game engine. Consider a third framing that fits Lovable perfectly: "world" — as in "I built a new game inside the BlockCraft world." It sidesteps the hardware baggage of "console" and the jargon of "engine," and it matches how remix-based creation actually feels.
Tie it back to the Nintendo/Sony story: when your students build on someone else's platform, they're making a bet on that platform. A great class conversation is: "If the platform you built on disappeared tomorrow, what part of your game would still be yours?" That's the Sony lesson, in kid form.