The trials and tribulations of HTML video in the post-Flash era
Adobe reversed course on its Flash strategy after a recent round of layoffs and restructuring, concluding that HTML5 is the future of rich Internet content on mobile devices. Adobe now says it doesn't intend to develop …
Context & Ripple Effects
Adobe's retreat has been building all year. In March it shipped Wallaby, a converter meant to smuggle Flash content past Apple's blockade by translating it to HTML5 — a workaround that only made sense while Flash itself remained the authoring format. By October 2010, [[a:1188699|Apple's refusal to support Flash had already pushed HTML5 video to majority adoption on the web]], and Adobe hedged with its own HTML5 Video Player widget for Dreamweaver. The November 2011 announcements end the hedging: layoffs and restructuring confirmed this month, followed by Adobe's statement that it will stop developing Flash Player for mobile browsers, capping support at Android 4.0 Ice Cream Sandwich with nothing for Android 5.0.
The scope is wider than phones. Two days before this piece, Adobe confirmed it was also abandoning Flash application work on TV devices, meaning the mobile capitulation is part of a single strategic pivot toward HTML5 and AIR-packaged apps across every non-desktop screen.
First-order effects
- Android device makers and carriers shipping Ice Cream Sandwich get one final Flash release by end of 2011, then no upgrade path — any handset promising future Flash support is now making a promise Adobe has publicly withdrawn.
- Adobe's own tooling customers face an immediate fork in the road: Flash-authored rich content must be re-targeted to HTML5 or wrapped in AIR, and Wallaby-style conversion goes from side project to core workflow.
Second-order effects
- Browser and chipset vendors who maintained Flash compatibility layers for mobile lose their reason to do so, freeing engineering resources that will flow toward HTML5 video performance instead.
- Competing mobile platforms gain a parity argument: with Adobe itself declaring HTML5 the future of rich mobile content, the 'Flash gap' ceases to be a differentiator against platforms that never supported it.
Third-order effects
- If the pattern holds, plugin-based media runtimes give way to native browser standards as the delivery layer for web video and interactive content, shifting power over rich-media features from Adobe's release cycle to browser vendors and standards bodies.
- Content publishers who built libraries on Flash face a structural migration cost, favoring shops already fluent in HTML5 toolchains and accelerating consolidation around whichever authoring tools Adobe pivots to next.
The trend: Mobile computing is forcing proprietary web plugins into retirement, with Adobe's own retreat confirming HTML5 as the default runtime for rich content outside the desktop.