Clarifications on Flash Player for Mobile Browsers, the Flash Platform, and the Future of Flash
I have worked with Flash and been part of the Flash community for about 12 or 13 years (over 10 of those with Macromedia and Adobe). Over that time there have been a lot of ups and down …
Context & Ripple Effects
This post lands at the end of an eighteen-month arc that began when Apple kept Flash off iOS and a Flash-versus-HTML5 debate broke out across the industry in early 2010. By August 2010 reviewers were calling the Android player a mobile Flash fail that proved Jobs right, and by March 2011 Adobe itself was hedging with Wallaby, a tool for converting Flash content into HTML5.
First-order effects
- Mobile developers who built on Flash Player in the browser lose their deployment target on day one, and are pushed toward Adobe AIR or native HTML5 instead.
- Adobe absorbs the cost directly: the same week it announced the mobile-browser retreat and the abandonment of Flash applications on TV devices, it confirmed a restructuring eliminating 750 jobs across North America and Europe.
Second-order effects
- Device makers and carriers lose the 'full web' selling point they used against Apple, removing the main competitive argument for shipping Flash-capable handsets.
- Tooling and conversion becomes Adobe's new battleground — Wallaby signals the company repositioning its authoring franchise around exporting to HTML5 rather than defending the player runtime, while rivals in HTML5 video and advertising tooling gain an opening.
Third-order effects
- The episode cements a structural lesson: platform gatekeepers that control what runs in their browsers can force a de facto standard retirement, regardless of installed base.
- If the pattern holds, cross-platform rich-media delivery consolidates around open web standards plus packaged-app shells like AIR, ending the era of a single proprietary plugin as the web's universal runtime.
The trend: Mobile computing is shifting the web's rich-media layer from proprietary browser plugins toward HTML5, with platform owners rather than plugin vendors deciding which runtimes survive.