Frequently asked questions

General questions

What is the Open Screen Project™?
The Open Screen Project is an industry-wide initiative, led by Adobe with the participation of other industry leaders, with one clear vision: Enable consumers to engage with rich Internet experiences seamlessly across any device, anywhere.
Which companies are participating in the Open Screen Project?
Open Screen Project partners are leaders in the mobile, desktop, and device ecosystems, each contributing unique knowledge and expertise in an environment of collaborative innovation. Among the over 200 participants are Adobe, Antena 3, Atlantic Records, ARM, BBC, Burda Digital Systems, CELL, Chunghwa Telecom, Cisco, Comcast, Conde Nast, Daum, Disney Interactive Media Group, Fox Mobile, Google, HTC, Intel, LG Electronics, Lionsgate, Marvell, Motorola, MTV Networks, NBC Universal, Nokia, NTT DOCOMO, NVIDIA, OpenTV, Palm, QNX Software Systems, Qualcomm, RIM , RTL, Samsung, STERN, Sony Ericsson, Texas Instruments, The New York Times, Tomorrow Focus Technologies Gmbh, Toshiba, Verizon Wireless, and ZiiLABS.
What will the Open Screen Project partners accomplish?
Partners in the Open Screen Project are working together to provide a consistent runtime environment for web content and standalone applications — taking advantage of the Adobe® Flash® Player and Adobe AIR® runtimes — this is removing barriers for developers and designers as they publish content and applications across desktops, mobile phones, tablets, televisions, and other consumer electronics. The Open Screen Project addresses potential technology fragmentation by enabling the runtime technology to be updated seamlessly over the network on mobile devices. The consistent runtime environment provides optimal performance across a variety of operating systems and devices, and ultimately provides the best experience to consumers.
What is Adobe doing in support of the Open Screen Project?
To support the mission of the Open Screen Project and as part of the company's ongoing commitment to enable web innovation, Adobe will continue to open access to Adobe Flash technology. This work will include:
  • Removing restrictions on use of the SWF and FLV/F4V specifications: Effective May 1, 2008, Adobe removed the entire licensing agreement from the SWF and FLV/F4V specifications. These licensing restrictions had meant that no one could build software that would "play" SWF content.
  • Publishing the Mobile Content Delivery Protocol (formerly known as the Flash Cast® protocol) and the AMF protocol for robust data services: The AMF protocol was published in February 2008 as part of the BlazeDS open source initiative at opensource.adobe.com. Developers can use the AMF binary format for exchanging data. It is most commonly used to transfer data between an application built with Adobe Flash or Flex® software and a database via a remoting request. Published in September 2008, the Mobile Content Delivery Protocol is a communication protocol that provides a mechanism for data to be synchronized between mobile phones and a network-based server in an efficient, mobile network–friendly manner.
  • Publishing the Real Time Messaging Protocol (RTMP) specification. Published in June 2009, the protocol is designed for high‐performance transmission of audio, video, and data between Adobe Flash Platform technologies.
  • Removing licensing fees: Adobe has made the newerxt major releases of Flash Player (10.1 and onwards) and AIR(2.5 and onwards) for devices royalty free — across all platforms, desktops, and devices — for Open Screen Project participants. Adobe Flash Lite® software isare not affected with these changes.
  • Providing The Open Source Media Framework (OSMF) for creating Flash video players. OSMF has a pluggable and extensible architecture and supports the workflows around video playback, like advertising and reporting, and enables the latest features of the Flash platform. OSMF provides an open standard video player – production-ready code that can be incorporated into customers' websites.
  • Publishing the device porting layer APIs for Adobe Flash Player: The device porting layer APIs enable Flash Player and Adobe AIR technologies to be delivered on devices without direct support from Adobe.
Why is Adobe spearheading this project?
The digital explosion across multiple screens is raising consumers' expectations for engaging experiences wherever and however they connect with content. Web browsing on mobile devices has become commonplace, but delivering a complete rich Internet experience on devices remains a challenge, and fragmentation and deployment barriers still limit innovation in applications and services. Adobe and the other companies working on the Open Screen Project want to provide an environment in which consumers can engage with great content and applications without boundaries from any device. For this vision to become a reality, a consistent application runtime needs to be available across desktops and devices.
What is the Adobe Flash Platform?
The Adobe Flash Platform is the de facto standard for delivering breakthrough applications, content, and video on the web. Flash Player and Flash Lite are on 98 percent of connected computers and more than 1 billion devices, and deliver more than 80 percent of web videos worldwide, helping to ensure that content and applications are presented consistently in the format users want.
Why are other companies participating in the Open Screen Project?
Companies contributing to the Open Screen Project share the vision that a consistent runtime environment removes barriers for delivering content and applications across screens. A more open and universal runtime across devices drives rapid innovation that ultimately is good for consumers. By removing barriers to the deployment of rich multiscreen experiences, all parts of the industry value chain can benefit from new revenue opportunities, cost efficiencies, and faster time to market in delivering more engaging devices, software, and services. Participants in the Open Screen Project have an opportunity to contribute to achieving this vision in collaboration with other thought leaders in the mobile, personal computer, and consumer electronics industries.
Can other companies participate in the Open Screen Project?
Companies and developers that would like to participate should see the instructions on how to license Adobe Flash Player and/or Adobe AIR by clicking here.
Why are over-the-network and over-the-air (OTA) updates important?
One of the primary goals of the Open Screen Project is to reduce fragmentation by providing a consistent application runtime for developers. With the ability to update Flash Player and Adobe AIR over the air and via the network, developers and content providers can create content that leverages the latest features and functionality of the runtimes, without having to wait months or even years for the latest version to be embedded on devices, or for devices with the latest runtime preinstalled to reach significant market penetration.

Benefits to the ecosystem

How do developers, designers, and content providers benefit from the Open Screen Project?
With a consistent runtime environment deployed broadly across devices, millions of developers and designers are able to distribute content to consumers worldwide, on virtually any device, much more easily than they could before. The Open Screen Project aims to maintain compatibility across devices, supporting rapid innovation and enabling devices to be seamlessly updated with the latest runtimes. As a result, time to market and development costs for rich Internet applications, interactive content, and video are dramatically reduced. Tight integration between the runtimes and Adobe's award-winning software tools helps ensure the ability to develop once and deploy everywhere through an agile design and development workflow. Developers and content providers also benefit from new revenue opportunities through increased customer reach and more open distribution models for content and applications on devices.
How do chipset vendors benefit from the Open Screen Project?
By including and optimizing the consistent runtimes into reference architecture designs and systems on a chip, chipset vendors can provide a more complete and integrated solution for original equipment manufacturers (OEMs). Chip makers can expect increased chipset demand and value through an integrated, consistent runtime environment that takes advantage of new hardware capabilities and encourages millions of developers to create rich content and applications. This results in greater adoption of their platforms for engaging with rich media.
How do OEMs benefit from the Open Screen Project?
Consistent runtimes across devices and open distribution models allow OEMs to tap a vast network of creative talent that can deliver more innovative and richer content and applications efficiently. This ultimately results in driving sales of feature-rich, higher average selling price (ASP) devices and incremental service revenues. Moreover, OEMs benefit from lower bill of materials (BOM) costs through royalty-free runtimes.
How do operators benefit from the Open Screen Project?
The Open Screen Project aims to enable seamless delivery of rich content and applications across multiple screens, placing operators in a position to provide more engaging and integrated "triple-play" services across broadband, mobile, and TV networks. As a result, operators can expect accelerated data services adoption and revenue growth. Also, operators benefit from lower content management costs and version complexity by leveraging a consistent runtime environment across device models.
How do end users benefit from the Open Screen Project?
End users benefit from more consistent rich Internet experiences that are connected across devices, as well as from greater choice in content and applications. Ultimately, the Open Screen Project brings about new ways for end users to engage with ideas, information, and people across all screens —— playing to personalized interests, communities, and interactions.

Open specifications, licensing restrictions, and royalty fees

Why is Adobe continuing to open access to Flash technology?
Publication of an unrestricted SWF file format has been requested by the Adobe Flash developer community. The long-standing publication of the SWF specification has fostered a vibrant ecosystem of companies and developers that create experiences with Adobe Flash technology, and by removing the SWF licensing restrictions, we are allowing that growing ecosystem to use the file format for any purpose, including the ability to play back SWF content. Additionally, Adobe has made Flash Player and Adobe AIR for devices royalty free as part of the Open Screen Project, for devices, along with publishing the device porting layer APIs and providing open source code around video player development. As a result of these moves, OEMs, software developers, and content owners are able to deliver content and applications built with Flash and AIR technologies without concerns about device restrictions. By removing the licensing cost and restrictions, as well as opening up the protocols and porting layer, Adobe is making it easier for developers and partners to deliver more engaging experiences to more of their customers and is helping to ensure that audiences can engage with content no matter what device or medium they use.
What other open efforts does Adobe participate in?
Adobe is active in working with open source, open specifications, and open standards. Over the last few years, Adobe has released major technology programs as open source, such as the Flex framework, the Flash Ajax Video Component, BlazeDS, and XMP. Additionally, Adobe contributed the ActionScript® Virtual Machine to Mozilla's Tamarin project, and Adobe is working with Mozilla on "Tamarin-Tracing," a release to the project that is focused on better performance across a wide variety of devices. Adobe also opened the specification for AMF and completed the commitment to move PDF into ISO, which is now international standard ISO 32000. Adobe is a member of the Linux Foundation, the Eclipse Foundation, and the SQLite Consortium. Adobe also introduced a public Flash Player bug and issue management system that allows greater community participation and transparency in the Flash Player development process. Early work on projects is also available openly on Adobe Labs to encourage early feedback and iteration. More information about Adobe open source efforts can be found at opensource.adobe.com.
What is Open Source Media Framework (OSMF)?
OSMF, part of the project previously code-named Strobe, is a standard open source framework that simplifies media player creation for the Flash Platform. Its extensible plug-in architecture provides production-ready code that meets recurring development challenges while helping publishers monetize their video content through seamless integration with partner services. With support for the latest player features such as Dynamic Streaming and DVR functionality, OSMF enables Adobe tool users and ecosystem partners to fully utilize the powerful video features of the Flash Platform. To learn more, read the detailed FAQ on OSMF.
What is the difference between the announcement made at NAB for Strobe and this new announcement for OSMF?
At NAB, Adobe announced a project under the code name Strobe. OSMF is the new release name for Strobe and represents the open source component of the previously named Strobe initiative.
Why is Adobe supporting OSMF?
By providing open standards around video player development, Adobe is reducing fragmentation and complexity in creating video players in the marketplace and advancing the Open Screen Project vision with the ability of its participants to further their online media efforts. Content partners can now focus on the overall user experience of video on their sites and spend less time on the technical details of building video players.
What is the RTMP Specification?
The Real-Time Messaging Protocol (RTMP) is designed for high-performance and efficient transmission of audio, video, and data between Adobe® Flash® Platform technologies. The open specification is available on the Adobe Developer Connection at the RTMP Technology Center.
What is the SWF file format specification?
The SWF file format specification is used to deliver vector graphics, text, video, sound, and interactivity via Flash Player and Adobe AIR. SWF files can reach over 98% of Internet-enabled desktops and more than 800 million handsets and mobile devices.
What is the FLV/F4V specification?
An FLV file encodes synchronized audio and video streams. The audio and video data within FLV files is encoded in the same way as audio and video within SWF files. The F4V format is based on the format specified by ISO/IEC 14496-12, the ISO base media file format. The FLV/F4V specification documents the file formats for storing media content used to deliver audio and video for playback in Flash Player and AIR. FLV and F4V are the de facto standards for web video today. More than 75% of broadcasters who stream video on the web use the FLV/F4V formats.
What are the device porting layer APIs for Adobe Flash Player?
These are device-specific abstractions of Flash Player that enable it to work on different operating systems and devices.
Why are the SWF and FLV/F4V specifications separated?
The SWF format is the binary file format, and the FLV/F4V formats are media container formats.
What motivated Adobe to remove the licensing restrictions from the specifications?
The SWF specification has been published since 1998. Until now, the specification had a license agreement associated with it, which said that developers could write software to output SWF but could not make software that would "play" SWF files. These license terms were initially included to prevent fragmentation, which most client technologies have experienced. These terms have worked well for Flash Player over the past decade as it now reaches over 98% of personal computers on the web with a consistent runtime, enabling things such as the video revolution we see today across the web. Adobe has removed this restriction from the SWF specification, as we have established a consistent runtime and we want to ensure the industry can confidently continue to support the SWF format. This permits the development of applications that play SWF files. Adobe, of course, remains focused on making the best, most reliable, and most consistently distributed implementation across desktops and devices.
Will Adobe continue to update the open specifications?
Yes, Adobe will continue to update and maintain the specifications as required to support future versions of Flash Player.
When will the SWF and FLV/F4V specifications be available without restrictions, and who will be able to access them?
The license restrictions were removed as of May 1, 2008. More details on using the specifications without the previous license restrictions are available on the Adobe Developer Connection at the SWF Technology Center and the FLV/F4V Technology Center.
What is the Mobile Content Delivery Protocol?
The Mobile Content Delivery Protocol is a communication protocol developed by Adobe as part of its client-server solution for mobile operators. It is available at the Mobile Content Delivery Protocol Technology Center. The protocol provides a mechanism for data to be synchronized between the mobile phone and the network-based server in an efficient, mobile network–friendly manner. The protocol is used in the Flash Cast solution that has been deployed with multiple operators around the world and is used transparently by millions of consumers as part of an engaging mobile experience.
What is AMF?
AMF is a binary format for exchanging data. It is most commonly used to transfer data between an application built with Adobe Flash or Flex software and a database via a remoting request. The AMF specification is available at opensource.adobe.com.
If I develop my own SWF applications that are compliant with the SWF specification, do I receive a license to use the codecs that are referenced in the specification?
What Adobe announced is the release of the SWF specification without the license agreement. The specification has never included a license to third-party technologies like codecs, which is still true today. Thus, developers of SWF-compliant applications are responsible for ensuring that their implementations do not infringe on the intellectual property rights of others, including those of codec providers.
Will the embedded codecs in the Flash Player and Adobe AIR runtimes also be royalty free? Do they require a separate license?
Licensees and users of Flash Player and Adobe AIR do not need to obtain a separate license or pay codec royalties for the use of the codecs when included in Flash Player and AIR. Organizations that wish to employ the codecs for any use other than as part of Flash Player or AIR will need to obtain the appropriate codecs from their owners, and license them as necessary.
Where are the new licenses for the SWF and FLV/F4V specifications?
Adobe has removed the entire license agreement from the SWF and FLV/F4V specifications. The only remaining restrictions are on copying and distributing the specifications themselves and on the use of Adobe trademarks, including the Flash trademark. The copyright and trademark restrictions are on the copyright page of the specification. Developers are now free to implement what is documented in the specifications without restrictions from Adobe.
Does this mean that it is possible for companies or developers to distribute Flash Player within their product offerings?
Adobe has removed the restrictions on the SWF and FLV/F4V specifications, not on Flash Player itself. Future versions starting with the next major versions of Flash Player (10.1 and onwards) and AIR (2.5 and onwards) for devices are royalty free as part of the Open Screen Project. However, a license (contract) still needs to be in place between Adobe and the licensee.

Open Screen Project Fund

How do I apply to the Open Screen Project Fund?
We are no longer accepting applications for the Open Screen Project Fund. We encourage you to visit the Adobe Developer Connection and specifically the Mobile and Devices Developer Center to learn more about how to create and optimize content for delivery across multiple screens.
How do I find out about past funding programs or applications?
For applications already funded, see the application showcase gallery.
How was the Open Screen Project Fund spent?
The Open Screen Project has funded more than 80 applications across 30 countries. Many of these applications are featured in the showcase gallery.