September 11, 2010
Following a trend of relaxing restrictions in its app acceptance policy, Apple on Thursday announced that it would no longer ban iPhone applications written in other languages from its app store subject to certain provisions (which would exclude Adobe AIR). While Apple made a strong case as to the risks that third-party development tools made to the platform, I argued that, for many Flash developers, the choice was probably between using Flash or no app, as opposed to Flash versus Cocoa. And, of course, there’s nothing about Apple’s tools that prevent developers from making a bad app. The now more-transparent review process can be the point of quality control in either case.
In any case, it’s a win for Flash, and that means a win for Adobe, right? In its response to the announcement, Adobe reminds that Apple still does not allow Flash to run natively on iOS devices. No, the allowing of apps with the Flash cross-compiler is ultimately not the native Flash home run Adobe really wants. But, had Adobe kept in there, swinging away and pledging to continue to work with Apple to address the issues Apple has with Flash and the cross-compiler (regardless of the realism of that prospect), it would have a better story to tell now. It could have shared some level of responsibility in helping to convince Apple of the cross-compiler’s value (Adobe is, after all, an iOS developer), which opens up the the three (installed) bases of iPhone, iPod touch, and iPad to Flash developers.
But that’s not what Adobe did. In April, Adobe CTO Kevin Lynch blogged that Adobe was moving forward from iOS. And in August, frustrated by the impasse, Adobe CEO Shantanu Narayen noted in reference to Apple, “They’ve made their choice. We’ve made ours and we’ve moved on.” Adobe was too eager to close the door when, clearly in hindsight, it had a chance to be reopened. Apple has cracked the door open to Flash developers a few months after Adobe decided it wouldn’t even drive them to the party.
Now, of course, Adobe is resuming work on the Flash cross-compiler for iOS. But can you imagine if Microsoft was so quick to shrug its shoulders when trying to advance its platform? “Sorry, guys. Mobile’s been a tough nut for us to crack. Android seems to be getting pretty popular now, though, so maybe you should consider casting your lot with that.”
Tags: Adobe, cross-compiler, Flash, iPhone
February 9, 2010
Hulu is anytime, anywhere enjoyment of some of your favorite TV shows — as long as your PC can be used in those circumstances. With Flash coming to nearly every smartphone save for Apple’s many are looking forward to enjoying their House outside of their home.
But first, there’s the realities of even today’s most advanced smartphone processors and even more limiting wireless networks. Apparently, using the latest Flash beta for the Snapdragon-powered Nexus One, you can get up to about 17 frames per second for standard-definition Hulu content (360p) and that’s using Wi-Fi.
That’s not bad, for as long as it lasts. But there may be issues in preserving compatibility with smartphone Flash as Hulu rolls out new DRM. More serious, of course, is whether Hulu, or its content partners, or its content partners’ cable customers, want you to watch Hulu on your smartphone as Hulu is authorized only to deliver video to the PC. If any of those parties decide that they don’t want Hulu being watched on handsets, we could see a redux of the recently reignited Boxee block.
I suspect it will not pan out that way, but I also would be somewhat surprised to see Hulu negotiating with the carriers or creating their own smartphone applications. Perhaps the networks will go it alone or perhaps they will anoint some new puppet aggregator to manage wireless distribution.
Tags: boxee, Flash, hulu, NBC, smartphones
March 5, 2008
Over at News.com, Coop joins the reaction to Apple’s “slam” of Flash, throwing in the Adobe reaction that both Flash and Flash Lite have been very successful, thanks so much. I’ve often marveled at how responsive Mac OS X feels on the iPhone. This was a thread that Jeff Atwood referred to in the post about Vista’s perceived performance. Jobs says simply that desktop Flash is too heavy for the iPhone, and that Flash Lite isn’t up to desktop performance. Essentially, he’s asking Apple Adobe to do the same thing Apple has done, which is to optimize desktop software for a mobile platform.
If you are an iPhone user, you have to read between the lines here because Jobs is essentially saying that Apple wants Flash on the iPhone (which is good news considering the scenarios I laid out as to why Apple might not) but just can’t accommodate it. That’s an engineering problem Adobe is motivated to solve given as iPhone sales grow and consumers do more mobile browsing on it.Adobe will get there. And let’s face it, few software companies have as long a history of supporting Apple technologies as Adobe.
We may not see it announced on the 6th, but Flash playback will come to the iPhone.
Tags: Adobe, Apple, Flash, iPhone, Steve Jobs