Mobile Flash apps get better distribution, more money
In advance of this week's Mobile World Congress in Barcelona, Adobe is making several announcements to encourage developers to build applications using its Flash and AIR platforms. The biggest announcements are a new distribution method …
Context & Ripple Effects
By early 2009, Flash had already reached feature phones through Flash Lite 3, but mobile remained a side channel for Adobe compared to its dominance on the desktop web. Ahead of Mobile World Congress, Adobe is attacking the two things that kept serious developers away: getting apps into users' hands and getting paid for them.
The move sets up a multi-year campaign that the rest of the corpus traces closely: Adobe later commits to shipping Flash on Android, WebOS and BlackBerry devices, courts iPhone developers with Flash-based tooling, and then — as the platform war turns against it — builds the Wallaby tool that converts Flash content to HTML before retreating from screens beyond the browser.
First-order effects
- Mobile Flash and AIR developers immediately gain an official distribution pipeline and improved revenue-sharing terms, lowering the barrier that previously pushed them toward carrier-specific or native development.
- At Mobile World Congress, Adobe hands handset makers and operators a ready answer to the app-store era: a familiar runtime with a large existing developer base they can showcase on new devices.
Second-order effects
- Apple's decision to keep Flash off the iPhone forces Adobe into workarounds rather than partnership — including tools aimed at compiling Flash applications for iOS — making Android, WebOS and BlackBerry the real battleground for the strategy.
- Device makers gain a low-cost way to differentiate mid-range hardware with rich media and apps, which pressures rivals without an equivalent runtime to lean harder on open web standards instead.
Third-order effects
- The episode becomes an early demonstration that on mobile, unlike the desktop web, the device owner controls distribution — a lesson that shapes how every subsequent cross-platform runtime (and its monetization model) has been judged.
- If gatekeeper-controlled stores keep winning developer mindshare, runtimes like Flash survive only by converting to the platform-native format — which is exactly where Adobe's own pivot to HTML conversion tooling points.
The trend: This is one data point in the broader shift from open runtimes competing on reach to platform-gated distribution deciding which developer ecosystems win — the pattern Adobe's later retreat from mobile Flash made explicit.