Adobe's Wallaby ties Flash to HTML
The toolkit converts Flash files to HTML so that they can run on Apple's iOS or WebKit-based browsers — Adobe Systems is making available this evening a preview of its Wallaby technology, which enables developers to leverage Flash development skills …
Context & Ripple Effects
Apple's refusal to let the Flash player onto iOS has boxed Adobe out of its richest distribution channel, and Wallaby is the company's second attempt at an end-run. The first, a 2009 push around building iPhone apps with Flash, collapsed when Apple barred the cross-compiler route; this time Adobe is not trying to smuggle a runtime past the gatekeeper at all, it is converting Flash-authored files into plain HTML so they run natively in WebKit.
The conversion playbook is already proven elsewhere in the ecosystem: Skyfire's iOS browser won Apple approval last November by translating Flash video into HTML5 on the fly, and Apple itself has explored a native alternative with its Gianduia project. Wallaby extends that logic upstream to the authoring side, letting designers keep working in Flash while the output targets the standards Apple permits.
First-order effects
- Flash developers gain a preview toolchain that repoints existing .FLA work at iOS and WebKit browsers, keeping Adobe's authoring franchise relevant on a platform where the Flash player is banned.
- Apple loses nothing immediately — the blockade stands — but the practical cost of ignoring HTML5 content drops for every site that runs Wallaby conversions instead of rewriting by hand.
Second-order effects
- Rival toolmakers face pressure to add one-click Flash-to-HTML export of their own, turning 'standards-compliant output' into table stakes for web design software rather than a differentiator.
- The economics of the standoff shift from runtime politics to authoring convenience: whoever owns the smoothest conversion path captures the migration budget of studios rebuilding iOS-friendly sites.
Third-order effects
- If conversion tooling matures, the plugin era ends not through negotiation between Adobe and Apple but through attrition — Flash content survives only as translated artifacts inside HTML5, and the browser vendor, not the format owner, sets what ships.
- Platform gatekeepers gain a durable template: block a proprietary runtime outright, then wait while the incumbent rebuilds its own ecosystem atop your approved standards.
The trend: Mobile platform gatekeeping is forcing rich-media vendors to migrate from proprietary runtimes toward HTML5 output, with automated conversion tools serving as the bridge.