Today, I gave a presentation to my fellow Ed Leaders on working with students to optimize Flash for mobile applications at the AEL Summer Institute in San Jose. There’s been a lot of criticism against Adobe that states that Flash crashes browsers, or uses too many resources, or takes to long to download. I’ve never found this to be the case. However, I have seen instances where a development could be optimized to make the activity look/feel better for the end user.
The presentation’s initial proposal was written to show users how easy it was to export AIR applications and seamlessly turn them into iPhone apps. But in early April, the rules changed due to Apple’s stance on Flash, and the change in wording in their developer license. Since I had to change the focus of the presentation anyway, I figured it would be good to discuss best practices for optimizing Flash. These are good rules of thumb in general. But, when it comes to mobile delivery of Flash apps, special considerations apply since you have limited memory, processing and screen size.
The gist of the presentation boiled down a 92-page white-paper by Thibault Imbert and Paul Robertson (Optimizing Performance for the Adobe Flash Platform) as well as some practical tips by others in the industry.
The video of the presentation will be on Adobe TV soon. I’ll post a link as it becomes available.