There's quite a bit of confusion about the impact of Adobe's decision (or what exactly the decision was) in regards to Flash Player of Mobile. Rightfully so, as the company didn't spell out its intent to its users at the same time it pushed out news to analysts during the 9 November analyst day briefing.
Besides the StreamingMedia.com article titled "Into (not so) thin AIR" (self-plug) there are two Adobe blog posts that may help explain where the company is going...or at least what it plans to still support:
Pritham Shetty's "Adobe Flash for Premium Video" blog post spells out what's in and what's out.
Mike Chambers's blog post, "Clarifications on Flash Player for Mobile Browsers, the Flash Platform and the Future of Flash" does a good job explaining the "why" of unsustainable growth in complexity Adobe faced in the wild-west atmosphere surrounding Android forking.
We conjectured, in the "thin AIR" article posted on StreamingMedia.com, that Android forking complexities could cause Adobe's costs to run rampant. It was helpful to get confirmation a few hours later, when Mike posted his Clarifications blog post, that Adobe had indeed seen this Great Wall of Android that it had to scale, and chosen a wiser path.
Besides the StreamingMedia.com article titled "Into (not so) thin AIR" (self-plug) there are two Adobe blog posts that may help explain where the company is going...or at least what it plans to still support:
Pritham Shetty's "Adobe Flash for Premium Video" blog post spells out what's in and what's out.
Mike Chambers's blog post, "Clarifications on Flash Player for Mobile Browsers, the Flash Platform and the Future of Flash" does a good job explaining the "why" of unsustainable growth in complexity Adobe faced in the wild-west atmosphere surrounding Android forking.
We conjectured, in the "thin AIR" article posted on StreamingMedia.com, that Android forking complexities could cause Adobe's costs to run rampant. It was helpful to get confirmation a few hours later, when Mike posted his Clarifications blog post, that Adobe had indeed seen this Great Wall of Android that it had to scale, and chosen a wiser path.
Posts
No comments:
Post a Comment