Archive for category Mobile World Congress
It’s Day 2 of the Mobile World Congress in Barcelona, and what a great start to the show. We have announced that Flash Player 10.1 is installed now on over 20 million devices, and AIR is available on 84 million. Those numbers are incredible, and well above expectations for the first six months after launch. In 2011 I predict that we’ll be looking at huge adoption curve throughout 2011 and I’ll be sure to update you as we grow the install base.
Most importantly, you have all been very busy it seems, with thousands of applications shipping across these devices and more to come.
The Blackberry Playbook is really becoming a hit with developers, everyone at the Blackberry events here is building something. We’re hearing great things from the community here, and this coming Friday we’ll have our yearly “AdobeDays” event at the Barcelona office. Let’s hope I make it until then!
Everyone on the stand has been hugely impressed with the device capabilities, and we’ve spent a lot of our time speaking with Java and Blackberry developers that are planning to create their first applications in Flash for the Playbook.
We saw the launch of the aptly named “Samsung Galaxy Tab 10.1″, and the Galaxy S II – which has really stolen the show in terms of design. Here is Adobe’s David Whadhwani, SVP/GM Creative Interactive Solutions BU on stage at the Samsung launch and talking about the successful relationship that we’ve had with Samsung for years now.
David also take the opportunity to remind the audience about AIR 2.5 for TV, and Samsung’s commitment to delivering support for your applications across their latest ranges – and that includes BlueRay Players. Samsung are almost the definition of why we created the Open Screen Project, we’ll obviously be talking a lot more about these devices later this year.
It’s almost that time of year again, the Mobile World Congress 2011 is set to be an amazing event with all of the major OEMs, Operators, Chipset vendors and our Open Screen Project partners in attendance. Some 50,000 attendees from across the world descending on Barcelona, showing their new devices, services and Developer offerings.
This year we’re going to be meeting our various partners, and the Evangelism team will be presenting alongside RIM for the Blackberry developer day. We’re really excited to be working so closely with our partners, and I can’t say I’ll miss the alarms going off at the device bar
As always, we’re working with our Mobile and Devices Spanish User Group to hold an event following the show. This is our forth year running this event, and I’m happy to say that it has become a major part of our activities during the show. As with last year, we’re going to make this a Spanish language event as much as possible.
So if you can understand Spanish, and delivery content for the Iberic region, this is a great event to attend. I know that Marcos and Raul have worked really hard to bring you a range of speakers and topics, and there are not many tickets left – so sign up now!
09.45am Cross-platform application development: Synctur
11.30am HTML 5 for mobile: Maximiliano Firtman
12.15pm Usability/Productivity: Justinmind
13.00pm Meet the Playbook
Surprise! Today at Google I/O Vic Gundotra, Google VP Engineering announced Flash Player 10.1 and Adobe AIR 2.5 running on FroYo. The launch today represents a milestone that we’ve been working towards for some time, and all of us at Adobe are hugely excited to see Flash Player 10.1 finally get into the hands of consumers.
The beta is now waiting on the Android Market for Nexus One and other Android 2.2 users to test out. General availability is expected in June 2010.
While today’s announcement is all about Android, our target mobile operating systems for Flash Player also include Windows Phone 7, webOS, Symbian, and BlackBerry. Adobe provides a porting kit and Linux-based reference implementation to Open Screen Project partners to allow them to port Flash Player 10.1 to other platforms. These ports are subject to Adobe certification and must pass our standards for compatibility, performance and usability in order for devices to be marketed as “Includes Adobe Flash Player.”
Flash Player 10.1 on Android
In all, Flash Player 10.1 has been built from the ground up, and not just for mobile phones but for the desktops, tablets, netbooks and even televisions, consoles and set-top boxes. We have been working extremely hard on the runtime of course, but on top of that many of you have been working with us to optimize your web content for Flash Player 10.1.
Here is a landing page that features a number of websites that highlight the variety of Flash Player user experiences available on a mobile device. These sites and most popular websites that use Flash can now be accessed on smartphones supporting Flash Player 10.1.
Since we demonstrated the Flash Player on Android at the Mobile World Congress there have been a number of decisions made, changes implemented and tweaks applied to Flash Player 10.1. These changes focused on usability, integration, performance and power management – so let’s look at some of these in more detail.
Installation and updates
I have documented the process over here in another post. Suffice to say, the process is simple and demonstrates our commitment with the Open Screen Project to ensuring the evolution of Flash Player on mobile and devices.
Due to time constraints with shipping FroYo it hasn’t been possible to make all of the Android browser changes required to enable multi-touch in Flash Player. Web enablement has always been the top priority and so this (extremely complex) integration will happen later. AIR 2.5 on Android is multi-touch enabled and so it’s still possible to use your fingers, thumbs and toes as necessary on Android.
One of the cool new feature of Flash Player 10.1 is the accelerometer API, making Flash Player the first browser technology to support access to this hardware. In Device Central CS5 we have added some emulation support for the API, you can read more here.
Focused Mode (single tap)
The Android and other browsers support multi-touch for viewing web pages, so that you can pan and zoom around non-optimized sites with ease. To ensure that touch events are received by Flash or the browser appropriately we have created focused mode. It works very simply using a priority system, so if you tap the Flash content that you want to interact with Flash receives the touch events, if Flash doesn’t pick up the event then it’s passed to the browser. Tapping on the HTML will revert this focus priority back to the browser.
Smartzoom (double tap)
When a user double taps a piece of Flash content it will zoom to fit the screen, while maintaining the correct aspect ratio. The content is still viewed in the context of the HTML, rather than launching into full screen mode. This ensures that content remains in embedded mode – which makes sense given that this is the predominant usage of Flash on the web.
Another change to our previous showing is that FullScreen mode is now controlled via actionscript, just as it is on the desktop. So if you want your video player or game to playback using the full screen, then you’ll need to use this code:
We have already seen some of the benefits of this effort on the desktop version of Flash Player 10.1. Essentially it means that Flash content that’s not visible to the user will not be rendered and will receive limited CPU time. SWFs that are off-screen and/or consuming required resources can also be put to sleep and resumed on demand. You can control this behaviour by applying priority values to SWF files using the embed tag.
Video Hardware Decoding
One of the hardest features to get right has been video hardware decoding, and for the beta version this will not be enabled.
The player will be put to sleep along with the device to conserve power. So if you fall asleep watching youtube then you won’t wake up to talking cats at 4am – tried and tested. cats…
For me, this is the kick-ass feature that should always have been arbitrating the use of the Flash Player. If your content is not optimized correctly, has serious memory leaks and manages to use too much CPU power then it’ll go in the “sin bin” These SWFs will render with a “click-to-play” button that the user can control as necessary.
As with Flash Lite before it, Flash Player 10.1 has to be a good citizen on a mobile phone. So if you receive a call or change application then Flash Player will respond appropriately, which typically means shutting down or pausing depending on the platform.
As has been documented before, our minimum spec for Flash Player 10.1 is ARM11-Cortex A8/9 at 550mhz. For Cortex-A8 processors we require NEON, which enables improved multi-media playback for a lower mhz rating.
If you don’t know what any of that means then I wouldn’t be too concerned. These chipsets represent the bulk of what our OEM partners are shipping, or planning to ship moving forward – and this list will undoubtedly expand.
AIR 2.5 on Android
Also announced today is an expanded pre-release of AIR 2.5 for Android devices. Many of us on the Evangelism team have been playing with this for several weeks now, and it’s seriously cool.
While I was at the Mobile World Congress earlier this year I recorded a quick video of sample tablet hardware running a beta version of Flash Player 10.1. It has taken a “little” while to arrive on Adobe TV, but in the video I’ll show some popular websites covering video and gaming.
The hardware is a development board sporting the ARM based NVIDIA Tegra Next Generation chipset, which is a dual-core ARM-Cortex A9 device. Although I didn’t show it here, at the conference we were also running AIR applications beautifully on the hardware.
Our Open Screen Project partners NVIDIA announced that some 30+ tablet computers are expected to ship in 2010 with this chipset. One of the advantages of having NVIDIA and ARM as Open Screen Project partners is that we can all contribute collectively to Flash Player acceleration for these devices. So as OEM begin to adopt TEGRA they can rest assured that the Flash engineering is already taken care of.
My favourite so far would have to be the NotionInk Adam, which is an Android based tablet created in India. The screen apparently has transmissive, transflective, and reflective display modes that will serve the device well in different lighting conditions.
Flash Player 10.1 will become available in the first half of 2010 for all supported platforms. In fact, the desktop beta 3 is already looking incredible and proving to be a huge hit with developers testing their content.
One of the most important parts of our work with our Open Screen Project OEM partners is to enable the seamless discovery, installation and update of Flash Player 10.1 on device platforms. I know that some have asked questions on this, and so I’m glad to bring you some responses, if a little late.
Extending the reach
In the “marketecture” diagram below you can see that Flash Player 10.1 is extending it’s platform reach, doubling it in fact. It’s worth noting that recent reports around minimum spec’s for Flash Player 10.1 are alluded to here also, because working with our partners, we are targeting the latest chipsets available.
To explain, smartphones have a typical lifespan that is less than half that of a desktop computer, and so hardware choices are made by planning for the future. Over the past few years we have shipped over 1.5Billion devices with Flash Lite using this simple rule.
Therefore the choice to target the ARM Cortex-A8 chipsets will result in greater efficiency, and most importantly a wider range of consistent experiences as uptake grows. To be clear, that uptake is already happening, and it will expand rapidly just like it does every other year.
It’s like a Moore’s Law of mobile phones
Yet some devices will not be able to support the full Flash Player 10.1 due to low hardware capabilities, and for many of those devices we have a new version of our optimized runtime, Flash Lite, to fill the gap. In fact the alpha version has already been spotted running Farmville on Android Eclair here.
Driving the Distribution
Working with our OEM partners we have enabled the Flash Player to be installed in a manner consistent with the desktop experience. When visiting websites that have Flash content, users can click on the “Flash Player required” images/links provided by content developers to begin the installation process.
As with the desktop, the browser then redirects to the Flash Player Download Center, and in the case of mobile phones we pass these requests to the requisite device application stores such as the Android Market. Today’s application stores have extended abilities to correctly identify devices, and to manage the update of applications and plugins like Flash Player. Users can of course visit their application store directly if they wish.
In addition, those users purchasing new devices from a retailer may already have Flash Player pre-installed, made available in over-the-air software updates or through the browser directly.
As with the desktop install process, with each version of the Flash Player various updates are applied throughout it’s lifetime to ensure a high level of quality. Users can expect these updates to be provided automatically on some platforms via their application store update process, as well as through over-the-air software updates.
In the example above you can see the update notifications that users are familiar with on Android devices, and it is expected that this will be used for Flash Player 10.1 during it’s lifetime. Though I should point out that Nokia have been providing their own update mechanism, directly in the browser for some time now with a huge user uptake.
During the past few days Palm have also begun to lay the ground for Flash Player 10.1 support by delivering their software update.
On the desktop today developers use a combination of methods to detect the Flash Player and version. Recognizing the need for a consistent approach, these same methods can be used on mobile phones in the future. Adobe recommends SWFObject2, an open source project that provides cross-browser support. It is also supported fully within our Creative Suite tools. SWFObject works across browsers and device platforms to detect the Flash Player and it’s version. Should an update been required, the tool can enable the ExpressInstall experience or provide fallbacks as required.
Historically I know some have invested considerable time and energy in device databases such as WURFL, which helped us to accurately distribute application installers to devices. With Flash Player 10.1 we need only be concerned about the browser use case, and so I would argue that we do not need to continue this effort long term.
I hope this information will help you build a picture of the huge efforts that our engineering and product teams have made. The mechanisms for discovery, install and update of the Flash Player 10.1 are a fantastic achievement, even though for some of you these may seem rather obvious.
With the Open Screen Project partners we are literally changing the ecosystem, enabling a more complete and consistent web experience on devices, and driving the industry forward with the Flash Platform in 2010.