Adobe Flash Player was, for most of two decades, how the web moved. First released on January 1, 1996 as FutureSplash Player, passed to Macromedia and then to Adobe with its December 2005 acquisition, Flash became the near-universal browser plugin for animation, games, and video — and on December 31, 2020 Adobe stopped supporting it, then activated a kill-switch that blocked Flash content from running on January 12, 2021. After twenty-four years, the runtime that built an era of the web was deliberately set to expire on a date, like milk.
At its height Flash was effectively ambient. Adobe claimed the player reached the neighborhood of a billion internet-connected desktops, present on essentially every browser that mattered; if a site had an intro animation, a banner ad, an embedded cartoon, a casual game, or — crucially — streaming video, it almost certainly ran on Flash. It powered Newgrounds, Homestar Runner, an entire generation of browser games, and the early years of YouTube. For animators and hobbyist developers it was the most accessible creative runtime ever shipped: draw, script a little ActionScript, export, embed.
What killed Flash was not a competitor product but a convergence of structural forces it could not answer. It carried chronic, well-documented security vulnerabilities that made it one of the most reliably exploited pieces of software on any machine. It was a CPU-hungry, battery-draining plugin built for the mouse-and-desktop world precisely as computing moved to touch and mobile — and in April 2010 Steve Jobs published “Thoughts on Flash,” refusing it on the iPhone and iPad and citing openness, security, performance, and battery life. Meanwhile HTML5, WebGL, and later WebAssembly absorbed, in the open browser itself, nearly everything Flash had done. Adobe announced the end on July 25, 2017, with Apple, Google, Microsoft, Mozilla, and Facebook coordinating the wind-down.
Flash’s death was unusually orderly and unusually total — a runtime, not a service, so there was no server to leave running. What it endangered was the content: tens of thousands of games and animations that existed only as Flash files. That, more than the player itself, is what people raced to save.
Picasa was the fast, much-loved desktop application for finding, organizing, and lightly editing the photos already sitting on your hard drive, and on March 15, 2016 Google stopped supporting it. First released by a small company called Lifescape on October 15, 2002, Picasa was acquired by Google in July 2004 and from that point given away free. It did something that, in retrospect, feels almost quaint: it scanned your computer, gathered every image into one clean library, and let you crop, retouch, tag faces, and make albums without uploading anything to anyone. For more than a decade it was the default answer to “how do I deal with all these photos,” and it earned a loyalty that outlived its own updates.
The end was announced on February 12, 2016, in a blog post titled “Moving on from Picasa” by Anil Sabharwal, the head of Google Photos. The desktop application would no longer be supported as of March 15, 2016; the companion Picasa Web Albums service would begin shutting down on May 1, 2016. The stated reason was consolidation: Google wanted to “focus entirely on a single photo service in Google Photos” rather than “divide our efforts across two different products.” Picasa was not failing. It was simply on the wrong side of a strategy.
That strategy was the cloud. Google Photos, launched in May 2015, was mobile-first, automatic, and stored everything on Google’s servers — the opposite of Picasa’s local, you-own-the-files model. Killing Picasa was a bet that people no longer wanted to manage a library on a machine they controlled; they wanted it managed for them, somewhere else. For most users that bet was right. For the considerable minority who valued Picasa precisely because it kept their photos on their own disk and out of anyone’s cloud, the discontinuation was a quiet eviction from a workflow that had no real successor.
The desktop app, notably, did not detonate. Google did not push a kill switch; the program kept running on machines that already had it, unsupported and slowly aging. But “still works for now” is not the same as “alive,” and Picasa joined the long ledger of beloved Google products retired in the name of focus — this time not because users left, but because the company decided where they ought to keep their pictures.
Internet Explorer was the browser that conquered the web and then spent a decade as the punchline of it, and on June 15, 2022 Microsoft retired the IE11 desktop application for good. Launched in August 1995 as part of the Microsoft Plus! pack for Windows 95, IE rode the most powerful distribution advantage in computing history — it came bundled with Windows, the operating system on nearly every PC on earth — to crush Netscape in the first browser war. By 2002 and 2003 it held roughly 95 percent of the market, a dominance so total it became the subject of a landmark U.S. antitrust case over exactly that bundling.
Then, having won, Microsoft stopped trying. With Netscape vanquished, IE6 — released in August 2001 — was left to ossify for years, becoming a byword for security holes and broken web standards that web developers cursed and corporate IT departments could not escape. While IE stood still, the web moved: Firefox arrived in 2004 with tabs and standards compliance, and Google’s Chrome, launched in 2008, was faster and cleaner. In May 2012, Chrome overtook Internet Explorer as the most-used browser in the world. IE’s share collapsed, and the program acquired its enduring second career — the thing you opened once on a new PC to go download Chrome or Firefox, and then never touched again.
Microsoft eventually accepted the defeat it had inflicted on itself. It replaced IE with Microsoft Edge in 2015, and on June 15, 2022, after more than 25 years, the IE11 desktop application officially retired and went out of support, progressively redirecting to Edge. Legacy compatibility was preserved through “IE mode” inside Edge, which Microsoft committed to supporting through at least 2029 — a tacit admission that decades of intranets and enterprise apps had been built to IE’s idiosyncrasies and could not simply be abandoned.
What IE leaves behind is the canonical story of how a monopoly rots. It did not lose because it ran out of users or money; it lost because, once unchallenged, it quit innovating, accumulated a mountain of security and standards debt, and watched faster rivals dismantle a position that had looked permanent. The browser that once was the internet for most people ended as a compatibility shim and a meme.
Windows Phone was Microsoft’s genuinely good third mobile operating system, and it died not for lack of quality but for lack of apps. Launched as Windows Phone 7 on October 21, 2010, it broke decisively from the iPhone-and-grid template with “Live Tiles” — dynamic, color-blocked panels that surfaced information on the home screen instead of static icons. Reviewers praised the design’s clarity and originality, and on the well-built Nokia Lumia hardware it had a real argument as the most distinctive phone you could buy. By 2017 active development had effectively ended; Microsoft confirmed the platform’s last release would reach end of support on December 10, 2019.
The cause of death has a name developers used at the time: the “app gap.” A modern phone is only as useful as its software, and Windows Phone never attracted the breadth of apps that iOS and Android took for granted. The pattern was a vicious circle — too few users to justify the cost of building and maintaining an app, and too few apps to attract more users. Headline services arrived late, in crippled form, or never at all, and every missing or outdated app was another reason for a buyer to choose an iPhone or an Android instead. The OS could be elegant; the ecosystem was empty, and the ecosystem is what people actually live in.
The bet that was supposed to break the cycle made the failure catastrophic instead. In 2014 Microsoft bought Nokia’s devices and services business for roughly 7.2 billion dollars, aiming to control the hardware and force scale. In July 2015 it wrote down approximately 7.6 billion dollars on that acquisition — more than the purchase price — and cut about 7,800 jobs, overwhelmingly in the phone division. The numbers told the story plainly: Microsoft had spent billions trying to buy its way into a market whose users were already locked into two other ecosystems, and the market refused to follow.
Windows Phone’s discontinuation is the textbook case of the app-gap death and of network effects that money cannot purchase. It was not killed by a rival feature or a scandal; it was starved. A platform with no users gets no apps, a platform with no apps gets no users, and Microsoft, despite all its resources, never found the lever to break that loop before the loop broke the product.