The 90-Second Demo That Killed Flash: How Steve Jobs Walked Onstage Without a Single Line of Code and Executed Adobe's $800 Million Business
🎭Iconic MomentsMay 20, 2026 at 8:29 AM·9 min read

The 90-Second Demo That Killed Flash: How Steve Jobs Walked Onstage Without a Single Line of Code and Executed Adobe's $800 Million Business

April 2010. Steve Jobs didn't write a blog post to kill Flash—he gave a demo. No charts, no benchmarks, just an iPad, a sofa, and 90 seconds that made Adobe's engineers realize their decade of work was over.

Steve JobsAppleIconic MomentsAdobe FlashHTML5iOSiPadProduct Launch

The 90-Second Demo That Killed Flash: How Steve Jobs Walked Onstage Without a Single Line of Code and Executed Adobe's $800 Million Business

April 3, 2010. Steve Jobs walked onto the stage at the Yerba Buena Center carrying an iPad and a newspaper. Behind him, a massive screen showed nothing but white space. No slides. No talking points. Just a leather sofa positioned stage left.

Four days earlier, he'd published "Thoughts on Flash"—a 1,685-word manifesto explaining why Apple would never allow Adobe Flash on iOS devices. The tech press called it arrogant. Adobe's CEO, Shantanu Narayen, went on CNBC and called it a "smokescreen." Engineers across Silicon Valley argued in comment threads about H.264 vs VP8, about open standards vs walled gardens, about whether one company should decide the future of the web.

But Jobs didn't come to debate. He came to demonstrate.

What happened in the next 90 seconds didn't just win an argument. It killed a technology that powered 75% of web video, employed thousands of developers, and generated $800 million annually for Adobe. Jobs didn't write a line of code to do it. He just sat down on that sofa, picked up the iPad, and showed the world what the web looked like when Flash didn't exist.

And the world realized it looked... fine. Better than fine. It looked inevitable.

The Empire Flash Built

To understand what died that day, you need to understand what Flash was in 2010.

Flash wasn't just a plugin. It was the creative layer of the internet. Every animated ad, every game, every video player, every interactive experience that made the web feel alive—Flash powered it. Homestar Runner, Newgrounds, FarmVille, YouTube's original player, every banner ad that had ever annoyed you—all Flash.

Adobe didn't invent it. Macromedia did, back in 1996, as "FutureSplash Animator." Adobe acquired Macromedia for $3.4 billion in 2005, and by 2010, Flash Player was installed on 98% of internet-connected PCs. Ninety-eight percent. That's not market dominance—that's oxygen.

Flash developers were rock stars. They commanded premium rates. They spoke at conferences. They had their own subculture, their own forums, their own inside jokes about timeline nesting and ActionScript gotchas. Learning Flash was a career move. Companies like Nickelodeon, Disney, and Nike had entire Flash teams.

And then the iPhone happened.

The Phone That Didn't Run Flash

June 29, 2007. The original iPhone shipped without Flash support. Adobe's engineers assumed it was temporary—a v1.0 limitation that would be fixed in software updates. After all, the mobile web was Flash. How could a real web browser not support it?

But months passed. iPhone OS 2.0: no Flash. iPhone OS 3.0: no Flash. By 2009, with millions of iPhones sold, the absence was becoming conspicuous. Adobe started showing demos of "Flash Player 10.1 for Mobile" on Android devices. They took out full-page newspaper ads showing iPhones with missing puzzle pieces where Flash content should be, with the tagline: "We ♥ Apple."

Behind the scenes, the relationship was toxic.

Apple's engineers had spent years dealing with Flash's technical problems. It was the #1 cause of Mac crashes. It drained batteries. It didn't support touch input. Its security model was a nightmare—every patch seemed to introduce new vulnerabilities. Adobe kept promising a mobile-optimized version, but Apple's team had tested early builds and they were... not good.

More fundamentally, Jobs saw Flash as an existential threat. If developers built their apps in Flash, they'd work everywhere—iOS, Android, desktop, everywhere. Apple would lose control of the platform. The App Store, the 30% cut, the careful curation—all of it depended on native apps.

So when Adobe announced "Flash CS5" with a feature that compiled Flash apps to native iOS code, Jobs lost it. Apple changed the iOS developer agreement to ban apps "created by a translation or compatibility layer." The message was clear: No Flash. Not now. Not ever.

That's when Jobs wrote the blog post.

"Thoughts on Flash"

April 29, 2010. Jobs published a six-section essay on Apple.com. No video. No PR spin. Just Jobs, writing like he was explaining something to a smart friend who didn't get it yet.

The post hit six arguments:

  1. "Open": Flash is proprietary. Apple prefers H.264, CSS, HTML5—open standards.
  2. "The full web": 75% of video is already H.264. Most Flash is ads and games.
  3. "Reliability, security, and performance": Flash is the #1 cause of Mac crashes.
  4. "Battery life": Video decoded in software drains batteries. H.264 has hardware acceleration.
  5. "Touch": Flash was designed for mouse-overs. Touch needs rethinking.
  6. "Most important": If developers use Flash, they depend on Adobe, not Apple, for platform innovation.

It was clinical. Devastating. And it landed like a bomb.

Adobe's stock dropped 3% in after-hours trading. Engineers on both sides started arguing in blog comments. John Gruber called it "the closest thing to a must-read Apple's ever published." Flash developers felt personally attacked—this was their livelihood Jobs was calling obsolete.

But words don't kill technologies. Demos do.

The Sofa, The Newspaper, The New York Times

Four days later, Jobs was back onstage for the iPad's official launch event. And this time, he had proof.

He sat down on the sofa. Picked up the iPad. Opened Safari.

"Let me show you The New York Times website," he said.

The screen filled with nytimes.com. No missing puzzle pieces. No "Install Flash Player" prompts. Just... the website. Articles, photos, videos. Jobs scrolled through it, tapped a video, and it played instantly. Full screen. Smooth. Native.

The audience applauded.

Then Jobs opened Time Magazine's site. More videos. More interactivity. Everything worked. He opened a few more sites. CNN. ESPN. Every one had quietly launched HTML5 versions specifically for the iPad.

"All of these websites have created their content using modern web standards," Jobs said. "No Flash required."

Ninety seconds. That's all it took.

He didn't argue about frame rates or battery tests or security vulnerabilities. He just showed the world that the web worked without Flash. And not just worked—it was better. Faster. Smoother. Battery-efficient. Touch-native.

Flash developers watching that demo realized something terrifying: their clients were already moving on. The New York Times hadn't called them to rebuild their video player. They'd just... switched to HTML5. And it looked fine.

The Collapse

What happened next was swift.

June 2010: Google announced YouTube would use HTML5 by default on iPad. The site that defined Flash video was abandoning it.

August 2010: Facebook's video player went HTML5.

November 2010: Adobe announced it would stop developing Flash Player for mobile browsers. They called it "refocusing priorities."

By 2012, even Adobe was shipping HTML5 animation tools. Flash CS6 was renamed "Adobe Animate." The Flash Forums turned into ghost towns. Job postings for "Flash Developer" dropped 70% year-over-year.

July 2017: Adobe announced Flash would be end-of-lifed on December 31, 2020.

December 31, 2020: Flash Player stopped working. Browsers removed the plugins. Millions of websites went dark. Entire archives of early internet culture—games, animations, interactive stories—vanished unless someone had converted them.

The Flash era was over.

What Actually Killed Flash

It wasn't Steve Jobs' essay. It wasn't Apple's ban. It wasn't even HTML5's superiority.

It was the demo.

Because in those 90 seconds, Jobs proved something crucial: publishers didn't need Flash. The pain of rebuilding their video players for iOS was less than the pain of losing iPhone users. And once they rebuilt for iOS, they realized they didn't need two versions—they could just ship HTML5 everywhere.

Flash's network effect reversed overnight. The more sites that dropped it, the easier it became for the next site to drop it. Browser vendors stopped prioritizing Flash updates. Security researchers stopped bothering to report vulnerabilities—why patch a dying technology?

Adobe's engineers knew it was coming. They'd been watching iOS adoption numbers. They'd seen the writing on the wall. But that demo made it public. It gave publishers permission to move on. It gave developers permission to learn JavaScript instead of ActionScript.

Jobs didn't kill Flash with superior technology. He killed it with inevitability.

The Ghost in the Machine

Flash's death broke the internet in ways we still haven't fixed.

Thousands of Flash games are gone forever. The Internet Archive's Wayback Machine is filled with holes where Flash content used to be. Emulators like Ruffle try to recreate the Flash runtime in WebAssembly, but they're incomplete, buggy, years behind.

An entire generation of web designers lost their livelihood. Flash developers with 15 years of experience found their skills obsolete. Some pivoted to HTML5 game engines. Some left tech entirely. The transition wasn't just technological—it was personal, brutal, career-ending for many.

But it also freed the web. Battery life improved. Security vulnerabilities dropped. Mobile browsing became viable. The web stopped being "that thing that works on desktops" and became the universal platform Jobs envisioned.

HTML5 video, Canvas, WebGL, WebAssembly—none of these technologies would have gotten funding and engineering effort if Flash was still entrenched. Its death cleared space for the modern web to grow.

The Legacy

Steve Jobs gave thousands of demos in his career. But the Flash demo stands apart because it proved something only he seemed to believe in 2010: you can kill an 800-pound gorilla by showing the world it's invisible.

Flash wasn't defeated by a better technology. HTML5 in 2010 was worse than Flash in most ways—harder to use, less mature, less consistent across browsers. Flash had better performance, better tooling, better designer workflows.

But Jobs understood something Adobe didn't: adoption isn't about technical superiority. It's about inevitability. Once publishers believed they could survive without Flash, they didn't need to wait for HTML5 to be better. They just needed it to be good enough.

That's what the demo proved. Not that HTML5 was superior. But that life without Flash was possible. And once that became thinkable, it became inevitable.

Adobe never recovered. Flash was 15% of their revenue. The loss triggered layoffs, strategy pivots, and a decade of identity crisis. They've rebuilt around Creative Cloud subscriptions, but the cultural trauma remains—they lost the technology that defined them.

For Apple, it was vindication. The iOS ecosystem exploded because developers had no choice but to go native. The App Store became the most profitable software platform in history. Every dollar spent on iOS apps was a dollar that might have gone to Flash-based web apps instead.

And for the rest of us? We got a web that works on phones. Video that doesn't drain batteries. Sites that don't crash browsers. Security patches that actually matter. The modern internet—responsive, mobile-first, touch-native—exists because Flash died.

Steve Jobs killed it with 90 seconds on a sofa.

No code. No benchmarks. Just a demo that made the impossible look inevitable.

✍️
Written by Swayam Mohanty
Untold stories behind the tech giants, legendary moments, and the code that changed the world.

Keep Reading