The Flash Platform has a long history of delivering Web innovation, and core to the Platform is Adobe Flash Player, our browser-based application runtime. Today, Flash Player is installed on nearly all Internet-connected desktops worldwide, and delivers rich content and interactive Web applications to a rapidly growing number of smartphones, tablets and netbooks. We continue to advance Flash Player through both my team’s work and through the contributions of the Open Screen Project, which includes almost 70 industry partners.
Google is a key participant in the Open Screen Project and shares our commitment to driving innovation on the Web. With this common goal in mind, Adobe and Google are collaborating to take the Flash Player experience to the next level by supporting a deeper integration with Google’s Chrome browser. Today, Google is releasing the initial integration of Flash Player with Chrome in their developer channel, behind a command line flag. Moving forward, Google will be including Flash Player in Chrome so users will always have the most current release and a safer and more seamless experience. To learn more about this integration you can visit the Chromium Blog.
Additionally, we are also working with Google, Mozilla, and the broader community on a new API that can provide a better way for all Web browsers and plug-ins to interact with each other. While the current NPAPI has served the industry well, it lacks the flexibility and power to support the pace of innovation we see ahead. We expect that the new API specification will offer some distinct benefits over the current technology available.
- The API will be operating system and browser-neutral, minimizing the chance of inconsistent behavior across platforms.
- The new API is being designed with the flexibility to allow plug-ins to more tightly integrate with host browsers.
- The new plug-in API will provide performance benefits since the host browser will be able to directly share more information about its current state.
- The tighter integration provided by the API can allow for a more secure browsing experience as it will be easier to unify security models and collaborate on security techniques, such as sandboxing.
We welcome and encourage the participation in the definition and development of this new API. To read more about this project, visit this page.
Our hope is that the robust integration between Chrome and Flash Player will serve as a showcase for more consistent, seamless, and efficient Web browsing experiences. We feel that this significant effort by both Google and Adobe will directly improve the speed of innovation and move the Web forward, benefiting the entire community of developers and end-users.
Sr. Director, Flash Player Engineering
In partnership with the team behind Adobe Labs, we are pleased to announce the launch of a new website designed to let our community help us improve Adobe AIR. The website, Adobe Ideas, allows you to submit ideas on how to improve AIR as well as vote and comment on existing ideas from others in the community. As you submit ideas, please be as specific as you can with your description, and let us know the problems you are trying to solve. In addition, our team will be using this website to communicate features that are actively in development.
Though we only launched this new website just a few days ago, we are already seeing a significant amount of traffic. We’re energized by the response so far and look forward to seeing your suggestions on Adobe Ideas!
Sr. Product Manager, Adobe AIR
Andrew Kirpatrick just blogged on the Adobe Accessibility blog about an important upgrade we are planning for accessibility in Flash Player, AIR and Flex. Specifically, we will use IAccessible2 from the Linux Foundation and the WAI-ARIA specification from the W3C. Flash Player already implements Microsoft’s MSAA API ,and IAccessible2 (IA2) is a more modern API that provides improvements to MSAA. Choosing IA2 will enable us to address user and developer needs and to ease interoperability with assistive technology vendors across all three major operating systems (Windows, Mac, and Linux). Note this is not a Flash Player 10.1 feature, but we wanted to demonstrate our commitment and identify the specific improvements we are making to improve support for the needs of computer users with disabilities. This work and related accessibility improvements are expected in the next major release* of the player.
* Yep, as always, I can’t provide you with a date on that one
If you’ve ever wondered about plugins for AIR applications, I just published a article called Extending AIR Applications With Plugins which hopefully should answer most of your questions.
The trick to writing a plugin architecture for AIR applications isn’t really so much plugin management (installing, loading, deleting, etc.) as it is plugin security. Plugins that are privileged enough to be really powerful also have enough power to be potentially dangerous, so before an end user installs one, he or she needs to know not only who wrote it, but also that the plugin wasn’t somehow modified prior to installation. That’s where code signing and validation come in.
The sample plugin architecture I wrote addresses both plugin management and security. The article contains plenty of background on plugin security as well as sample code for an application called "Pluggable SearchCentral" which you can see in action below:
For more on how to write your own secure plugin architecture, see Extending AIR Applications With Plugins.
Mike Chambers posted today about FlashCamp San Francisco, which will be held at the Adobe offices on April 16th. The event is free, and focuses on all of the work we have been doing around Flash Player 10.1 and Flash Professional CS5.
The player team’s own Jim Corbett and Trevor McCauley will be presenting sessions, and members from all of the platform teams will be at the event. This is a great opportunity to get up to speed on the latest in Flash Player 10.1 and Flash Professional CS5…plus you get to to meet and have a beer with product teams.
Registrations for FlashCamps generally fill up fast, so make sure to register if you are in the San Francisco Bay Area.
Register for FlashCamp San Francisco
Be sure to check out a very exciting blog post highlighting both Flash Player and Adobe AIR running on HP’s upcoming slate device.
Alan Tam, a product marketing manager here at Adobe, demonstrated both Flash Player and Adobe AIR applications running on the device:
Welcome to the Flash Player Team development team blog. I’m Emmy Huang , a Group Product Manager for Flash Player. The team wanted to start this blog to share with you information about how things work in Flash Player, why they work the way they do, tips, tricks, and other interesting behind-the-scenes details.
While there are several individual team bloggers, such as Tinic, Mike and Trevor, this blog presents an opportunity for the team at large to also contribute to the conversation. And of course, don’t forget about using the public bugbase to file bugs and feature requests!
The team is excited about using this blog to engage with the community, so stay tuned as I start to get various team members blogging here over the coming months.
Group Product Manager, Adobe Flash Player
p.s. Not that the engineers are capable of “marketing-speak”, but we’ll do our best to give you the straight story.