There has been a lot of buzz in the mobile space lately, and I suspect there will be even more around Windows Phone 7 at next week’s Microsoft Mix conference. One thing I wanted to clarify as it may have been lost in some of the other news is that Adobe and Microsoft are working together to bring Flash Player 10.1 to Internet Explorer Mobile on Windows Phone 7 Series.

I don’t have an eta or other specifics right now, but it is something that both Adobe and Microsoft are working closely together on.

Two of the things that Flash is often criticized for is that it:

1. Uses too much CPU
2. Performs significantly worse on the Mac than on Windows

This got me thinking about whether some quick tests would bear this out, and if so, whether it was isolated to just Flash content.

Below are some raw numbers showing CPU usage of various rich content across different browsers and operating systems. This includes video deployed via HTML 5, JavaScript / Canvas animations, Flash Video, and Flash animations. This is by no means a scientific study, but I do think the results show that:

Here are my slides from my FITC Amsterdam talk titled Building High Performance iPhone Applications with ActionScript 3 .

Sorry I ran a little short of time, but you can find all of the info in the slides.

Here is the link to the Simple Game Framework which I discussed during the session.

In response to my post on Mouse Events and hover in Flash Player content on touch devices, John Gruber raises an issue:

The problem, though, for a hypothetic Flash plugin that renders pages within web pages (as on traditional desktop browsers), is how to tell whether a tap-and-drag within a Flash element is supposed to scroll the entire web page or be passed as a mouse movement event to the Flash element. It can’t do both, and it can’t read the user’s mind.

So, the Interwebs is all a buzz again around the latest article that “proves” that Flash will not be useful on mobile devices (much less the iPad). From the article:

Current Flash sites could never be made work well on any touchscreen device, and this cannot be solved by Apple, Adobe, or magical new hardware.

That’s not because of slow mobile performance, battery drain or crashes. It’s because of the hover or mouseover problem.

You may have noticed that since September, the public Flash Platform (Flash Player, Flex, etc…) bug base has required a login in order to browse and view bugs. This was not the case when we initially launched the public bug base but after a number of issues (primarily caused by spam), we had to disable viewing bugs without registration.

Starting last night, we are rolling out some new updates and tweaks to the bug base, and will be doing some testing to ensure that the original issues are addressed. As of right now, you can once again browse the Flash Platform bug base without registration (although logging issues or commenting still requires registration). Over the next couple of weeks, you may see some changes in access as we test and ensure everything is working, but the ultimate goal is to allow viewing and browsing of entries without requiring registration.

Yesterday, Apple announced their new tablet device, the iPad. Even if you are able to step back from all of the hype and reality distortion field surrounding the announcement, it is still an impressive device, one which I would love to get my hands on.

However, as a developer and Mac user, I am increasingly concerned with Apple’s movement toward creating a locked down, and closed ecosystem and platform. A platform where Apple controls which applications developers can deploy, and which applications and content users can consume.

Sorry for the two month hiatus on posting. I was on a sabbatical and vacation from work for the last 6 weeks of 2009, and have spent the first couple of weeks of 2010 busy working on code, and preparing some events for the spring (more on that in another post).

Some of the stuff I have continued to spend a lot of time working on, has been building iPhone content using the Flash CS5 private beta. I have been doing a lot of work on trying to figure out how to get the best performance, and understand the limits of Flash content on the device. I plan to make a separate post on that in the next couple of days.

I have just completed running all of the performance tests for the ActionScript 3 Development Task Contest #1.

The result below are tentative until I have confirmed that the code follows the rules (and spirit) of the contest. If you see any issues with any of the top 5 submissions, please post them in the comments. You can view all of the entries in the contest’s GitHub repository.

You can download and view the results as a csv file here .

I have uploaded all of the entries for the ActionScript 3 Development Task Contest #1 to the contest’s GitHub repository.

If you sent me an entry and do not see it in the repository, email me ASAP (without the file). Adobe’s spam system can be a bit overzealous at times, but if I know you sent me something, I can find it.

Also, I have not validated all of the entries yet. I will do that later today or over the weekend. If you see any major issues in a submission, then post them in the comments (do not email me directly about it). My plan is to post the initial test results on Monday, and then finalize Monday night or Tuesday. However, I am traveling early next week, so that might slip a day.