Time and again the same scenario arises. An app is being built and it’s all going fine until the very end when performance issues start to appear.

Optimizing Flash performance is certainly the most boring part of Flash Platform development but it’s a cornerstone without which you, the Flex developer, can not do without.

An app is worth nothing unless you provide that effortless flow of interaction at all times.

There is not too much information on this topic as it is not the most interesting one but here are some simple guidelines that have helped me tremendously over the time, as well as a few great papers.

So far, of all the AMF frameworks I have been a proponent of AMFPHP and RailsAMF. I still don’t know RoR very well (working on it), but I’ve been using PHP for a long time and have grown to love it so AMFPHP was always my natural choice.

Now we have a new player in Flash Remoting arena – ZendAMF. Why should anybody care when AMFPHP was just fine?

A few reasons.

…and why would we go around doing that when there are perfectly good solutions out there for online spreadsheets? For instance Google Docs in which I still haven’t found a bug or a feature I’m missing.

Spreadsheets are necessary because people use them because they know how to use them. It is a straight forward interface that can yield good in high complexity situations.

Now most people want to use them online. And luckily there are plenty to go around.

Here is some follow up information from the Flex Camp Chicago ’09 Community Showcase presentation.

By this time, I am very happy and impressed with PureMVC. In combination with Flex Code Generator, plumbing downtime is minimal and the more you work on a project, the more you see the benefits.

Out of all visualization frameworks for Flash Platform that I came in contact with, Flare is looking like the most customizable. I also like it’s structure. At first I didn’t, but now I love the fact that Visualizations are based on Sprites. I find that good for performance and transitions. You have to do a little extra work, but you will be happy with the result. All in all, I’m sold on it for now.

Recently I’ve been working on a Flex prototype using the PureMVC framework. I will talk at length another time about just how much PureMVC successfully solves a lot of problems that we encounter in interface development and especially about how much this framework is important for all those complex interactions that we expect out of our RIA interfaces.

Starting out with PureMVC is not a particularly easy task. It is a good thing that there are decent documentation and examples, at least for AS3. At first when I read the documentation, it made sense only on a high level, but translating that high level understanding to code right away was out of the question. I solved this initial sticking point by looking at a couple of AS3 examples like CafeTownsend and EmployeeAdmin, where you can see how the framework works on the right size demo app, not too big and not too small.

Although it’s not too hard to set up Google Analytics tracking on Flash based web sites the traditional way by referencing JavaScript, there are still good chances for something to go wrong in the process and debugging it is notoriously hard. The good people at Google have provided the Flash Platform Developer community with a great “little” library that wraps the whole process and provides a good debugging mode.

You can see the site here. Come often as it will be updated on a regular basis.

The goal of this site is to shed more light on what is it that we do here at Pathfinder with the Flash Platform.
We would be very grateful to hear feedback about the site from any perspective.

Adobe Flash comes with a very useful feature for bandwidth profiling. It allows you to see how will your site/app act under certain network conditions.

Flex Builder unfortunately does not have that option so we have to look somewhere else for a solution for testing.

While there are many applications that simulate various network conditions, Charles stud up as the most practical for Flex developers, in my opinion.

There is many ways to skin Flex applications. To name some that I’ve used: Flex CSS, Programmatic AS3, Flash, Degrafa, Photoshop (JPG’s, GIF’s and PNG’s) and Illustrator.

What usually needs to happen on a project is a combination of some or all of the above. Not having a single point of reference for skinning creates quite a bottleneck.

From different approaches, two surfaced as having the best pipeline: Illustrator CS3 and Degrafa. If we are talking speed and ease of graphic design, I would now default to Illustrator CS3. For advanced skinning and interactions Degrafa holds first place.