InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Adobe Moves Towards Greater Flash Openness and Availability

Posted by Jon Rose on May 01, 2008

Sections
Development
Topics
Rich Internet Apps ,
Rich Client / Desktop ,
Java
Tags
Flash ,
Adobe ,
Flex ,
Adobe Integrated Runtime ,
Web 2.0
This week Adobe continued their push towards greater openness within their Flash based technologies. In a move greatly targeted at developers, major adjustments were made to eliminate the licensing restrictions and third-party fees for distributing the Flash Player runtime. The move hopes to address vendor lock-in concerns and further extend the availability of the runtime, specifically on mobile devices.

Over the last few years, Adobe has made a number of changes to open up their developer platforms (Flex and AIR). They began the push with the open sourcing of the Flex SDK, and most recently open sourced the core of their LiveCycle Data Service’s product with the BlazeDS project. The move this week is the next step in what has become a clear initiative of the company to provide an open Flash platform for developers and content creators to utilize.

This week’s announcement features the creation of the “Open Screen Project.” Adobe’s Ryan Steward details the goals of the project:
The goal of the Open Screen Project is to enable a consistent runtime environment across a wide variety of devices and desktops. As part of the project, the next major versions of the Flash Player and Adobe AIR for devices will have no licensing fees meaning you can distribute and deploy them anywhere.
The Open Screen Project announcement includes a few significant changes to accomplish this:
  • Removing restrictions on use of the SWF and FLV/F4V specifications
  • Publishing the device porting layer APIs for Adobe Flash Player
  • Publishing the Adobe Flash Cast protocol and the AMF protocol for robust data services
  • Removing licensing fees - making next major releases of the Adobe Flash Player and Adobe AIR for devices free
Adobe’s Mike Potter details the expected impact of these changes within the mobile device space:
Mobile development will also get a boost by the removal of license fees for distributing the Flash Player and Adobe AIR for devices. Handset manufacturers will not need to pay Adobe to install the Flash Player on their devices. Adobe hopes that this will result in 1 billion phones having the mobile version of Flash (currently FlashLite) installed on them.
In addition to Adobe’s hopes of increasing the Flash Player’s availability, they also expect the move to curtail concerns about Flash within the open web. Ryan Paul of Arstechnica.com sees the move accomplishing this:
The Open Screen initiative is a win for the open web and the Flash ecosystem. This will empower third-party developers and bring a wider range of choices to content distributors as well as to end users, and it seems likely that the growing amount of competition in the rich web content space will continue to push advancements toward openness that benefit everyone.
Adobe’s CTO, Kevin Lynch, details the benefits of the move for developers. In addition, you can always learn more about Flex development for the Flash Runtime at InfoQ.com.
Tamarin by James Ward Posted
  1. Back to top

    Tamarin

    by James Ward

    Thanks Jon for posting this. This is really exciting news! You forgot to mention Tamarin which was Adobe's first major contribution to Open Source.



    Viva La RIA Everywhere!



    -James

    www.jamesward.org

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.