Adobe still plans to release its Flash CS5 development tools in support of Apple’s iPhone, but in a blog post, Adobe’s product manager for Flash, Mike Chambers, writes: “[W]e are not currently planning any additional investments in that feature.” I read that as Adobe finally throwing in the towel, acknowledging that Apple doesn’t want, nor will allow, apps created with Adobe code on its mobile devices.
And although developers may feel otherwise, I believe Adobe is making the right decision. In fact, it probably should have made it sooner. Apple’s developer agreement actually pointed out such restrictions last November: “An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise.” More recently, via the terms of its developer program license agreement, Apple reiterated the fact that it doesn’t want any proprietary code running on its mobile devices. Simply put, this issue isn’t a sleeping volcano that is only now exploding — it’s been prolonged by Adobe in the hopes that Apple would back down and give people a choice as to what they want to use on their handsets. But whether it likes it or not, Adobe has to hitch its ride to another wagon, just the latest fallout from the “open vs. closed” battle.
Rallying cries of “we want choice” are understandable, but ignore the fact that Apple has a choice, too. Just like any other company that manufactures goods, Apple gets to choose what — and what doesn’t — go into its products. Which means the consumer is left to decide what it wants most: the polished but controlled ecosystem of Apple that leverages web standards or a competing handset that offers those same standards plus Adobe’s upcoming Flash products.
The consumer may not have to look much farther than Google’s Android platform, which, by some measures, is growing faster than Apple’s iPhone. While Adobe is committed to delivering Flash 10.1 before the end of June, the company continues to mention Android in statements it makes related to that delivery date. (Note: I’ve asked Adobe which other platforms will see Flash 10.1 in the first half of the year, but have not received a response.) Google, meanwhile, is rushing to support its Open Handset Alliance partner with a post on the Adobe blog by none other than Andy Rubin, VP of engineering for Android, who writes:
“Partnerships have been at the very heart of Android, the first truly open and comprehensive mobile platform, since we first introduced it with the Open Handset Alliance. Through close relationships with carriers, device manufacturers, developers, and others, Google is working to enable an open ecosystem for the mobile world by creating a standard, open mobile software platform. Today we’re excited that, working with Adobe, we will be able to bring both AIR and Flash to Android.”
With such public backing from Google, Adobe’s situation doesn’t appear as tenuous as it did earlier this week, although this future isn’t written yet. Content providers that are hedging bets by offering video both in Flash and H.264 format will likely continue to do so — they can’t afford to have their content unplayable on certain devices, so they’ll play both sides of the fence. And developers that use Adobe’s toolset will still have a large audience for their apps on other platforms. The more immediate impact could be that Apple pulls the existing iPhone apps created with CS5 — Chambers says there are “100+ on the store today,” which is fewer than I expected.
This article also appeared on BusinessWeek.com