Aesthetics

There’s no doubt about it – the iPhone is one of the sexiest pieces of hardware ever built. It’s a beautiful object straight from the future. The UI is slick, elegant, simple and miles ahead of the competition.

In comparison the G1 is a utilitarian, brick-like lump. It’s a bit like comparing a 1980’s Land Rover to a brand new Audi TT. Which you prefer comes down to personal taste. For the record, no one cares how cool your phone looks. Anyone buying an iPhone to improve their chances of getting laid has a sad series of disappointments ahead of them.

Speed

Although TechCrunch routinely bashes the G1’s speed, I’ve never had a problem with either the OS responsiveness or the web download speed. it. In my completely unscientific testing, the web download speed on the G1 consistently beats my friend’s iPhones.

Especially in nerd-friendly cities like San Francisco, AT&T’s 3G network is completely saturated with all the other iPhone users uploading videos of their cat. In comparison, T-Mobile’s 3G network is a traffic-free 6 lane highway.

Development Platform

Even ignoring Apple’s bafflingly opaque app approval process, developing for the iPhone is a pain. The iPhone’s arcane development process involves mastering pointers and memory management in Objective-C. AFAIK these skills are not transferable to any other platform. Developing for Android requires Java on Eclipse which seems much more reasonable. Also, the iPhone app store is already completely saturated. With Android usage about to explode, now is probably a good time to get into Android dev.

Openness

If you use are using an iPhone with Apple’s MobileMe, your personal data (email, contacts and calendar) is only transferable to another iPhone. Android seamlessly syncs with gMail, gCalender and Google’s contact list. If you use these tools it is trivial to switch between Android phones, or for that matter any device that can access the web.

A good example of the two company’s different attitudes toward data portability is Google’s Picasa versus Apple’s iPhoto. Both are great personal photo management applications. The difference is iPhoto locks you photos into a single monolithic proprietary file whereas Picasa works with your existing photo file structure. iPhoto does not allow you to share your library with anything except for other iPhoto instances.

Since Apple make money off hardware sales they are keen to lock you into their proprietary systems. Google are platform agnostic and have a proven commitment to keeping data sharable. The Data Liberation Front initiative is a good example of this.

Monetization Strategy

There is a big difference in how Apple and Google make money, and this has a profound effect on the nature of their phone OSs.

Apple make money on the iPhone by selling the hardware and by taxing you every time you use the app store. The app store offers no trials and no refunds. Apple takes 30% of every purchase. Apple want you to buy as many apps as possible. They are re-using the iTunes model that has been so successful in generating revenue for them.

Steve Ballmer touches on this in his much ridiculed quote:

“The Internet is not designed for the iPhone. That’s why they’ve got 75,000 applications — they’re all trying to make the Internet look decent on the iPhone.”

There is actually some truth to this quote. If I have a fast and full-featured web browser why do I need a Yelp app? I can just go to yelp.com. Why do I need a dictionary app when I can go to dictionary.com? Why do I need to buy a bunch of crappy games when I can find millions for free on the web? God knows how much some iPhone devotees have invested in their iPhone in terms of app purchases alone. I prefer to buy the hardware once, then get the content for free. That’s the beauty of the internet.

Related to this is the fact that Apple won’t allow Flash on the iPhone. They have a very good reason – if Flash ran well on the iPhone, half of the apps in the app store would become redundant. In contrast Google just signed up for the Open Screen Project and are committed to making Flash run well on Android. For better or worse, Flash is tightly ingrained into the web and any device that doesn’t support it is half-cocked.

Google’s monetization scheme is a lot more vague, long term and possibly nefarious. They can afford to give away Android for free in exchange for the potential to make money from mobile searches. In general, Google’s plan is to become so useful and ubiquitous that they become an indispensable part of all of our lives. After that, who knows? Since they have a virtual gold mine in AdWords revenue they can afford to put their efforts into long term world domination. (As an aside, does anyone understand how Google makes so much money from text ads that nobody ever clicks?)

Reliability

The iPhone hardware is beautiful, but if it fails at the same rate that my iPods have failed then I would be buying a new one every 6 months. The G1 is built by HTC who have a reputation for building solid, reliable products.

In terms of data reliability, it’s not controversial to say that Google’s engineering team are second to none. By contrast, MobileMe had an inauspicious start and has been up and down regularly since. Cloud based data management is just not Apple’s strength.

So for me it ultimately came down to who do I trust my personal data with: Apple or Google? I decided to embrace our new Google overlords and have since shunted all my data to their servers. If and when Google turns evil please don’t say I told you so.

What’s better than a YouTube video? Sixteen YouTube videos – in 3D!

This is a for-fun, proof-of-concept demo loading in multiple instances of the new YouTube chromeless player and displaying them with Flash 10’s native 3D . Warning – this demo will probably run at a crawl and may crash your browser.

When working with other Flash developers, I am sometimes surprised when they are not aware of some dev tools that I consider essential. I thought it would be useful to list out the tools that I use everyday as a Flash Developer. All of these tools are free and cross-platform unless otherwise stated. None of this will be news to the seasoned Flash devs, but some will find it useful. Let me know in the comments if I’ve missed anything.

Applications

Desktop apps and browser plugins.

• Firebug. This firefox plugin lets you view a HTML page’s elements load in realtime, among other things. Great for debugging dynamic data loading into a SWF. Essential for any web developer.
• Flash Tracer. Firefox plugin to view your SWF traces in the browser. Invaluable.
• MAMP (Mac) and WAMP (PC). MAMP is a one-click install personal webserver for the Mac. WAMP is the same for Windows. Useful for debugging load timing issues on your own box, especially when combined with a web-proxy throttler.
• Charles and ServiceCapture. These web-proxies allow you to view your SWF’s dynamic data loads in realtime. They also offer throttling, which lets you simulate slow web connection speeds (both are not free).
• IETester (PC). Allows you to run IE8, IE7 IE 6 and IE5.5 on Windows 7, Vista and XP. Good for debugging IE6 weirdness.
• Flash Builder. Everyone has their own favorite ActionScript editor, and this is mine. If you are still coding in the Flash Actions panel, now is the time to stop – you won’t regret it! Flash Builder is an Adobe product so you know it’s going to be well maintained. As a bonus it uses the industry standard Eclipse UI, so the shortcuts you learn with it can be transferred over if you choose to develop in some other programming language later (not free).
• Versions (Mac) and Tortoise SVN (PC). Source control is not necessary for smaller projects, but if you value your dev time and want to be able to keep multiple versions of your code available, it is a must. Versions (not free) is the nicest SVN client ever, and Tortoise is the most popular Windows SVN client.
• Free Ruler(Mac) and JR Screen Ruler (PC). These little apps allow you to measure pixels on the screen without having to do a screen grab.
• Pathfinder (Mac). A Finder replacement that is hard to live without once you are used to it. Includes tabs and a split pane for dragging and dropping. Not really a Flash dev specific tool, but I’ve seen enough people be amazed at seeing tabs in the Finder that it was worth including here (not free).

Flash Libraries

Why re-build the wheel? There are tons of great, free ActionScript libraries made available by generous and talented developers.

• TweenLite. The fastest, most robust and easiest to use Tween library out there.
• Away3D. The best 3D library out there. Although Papervision seems to win all the awards, from my experience Away3D has the most features and has the best documentation. Also has a great user forum.
• casalib. A great collection of robust utility classes. Check here before writing that utility class!
• SWFAddress. Has quickly become an industry standard for building flash sites that support deep-linking. Handles lots of gnarly browser specific issues so you don’t have to. Built on SWFObject which is so useful I didn’t even list it here
• Hi-ReS! Stats. A very handy little class to show when your SWF framerate is choking.
• BIT-101 MinimalComps. A set of ActionScript-only UI components for use in non-Flex projects. Very easy to use and small in filesize. The code is also worth looking at to see how to build a super simple component framework.
• as3corelib. A collection of utility classes by Adobe for handling encoding and serialization among other things.

Bookmarks

To round out this list, here are 3 webpages that I am always hitting:

• ActionScript 3.0 Language Reference. Why memorize stuff when you can look it up? Flash Player 10 version is here.
• Flash Player Version Test. When your client wants to know why your awesome site looks like a grey box on their crappy PC, send them here first.
• BrowserLab. A great free resource from Adobe to test your site on multiple browsers/OSs.

"Assignment within conditional. Did you mean == instead of =?"

How great is that? I used to work with a guy (who will go unnamed) who would threaten to sneak onto your machine and remove equal signs from equality tests in your code at random, because “the compiler would never tell you about it”. Thankfully, his evil plan has now been foiled

Maybe the compiler should also warn about equality tests that are not in conditionals and not on the right hand of an assignment. Would that be useful or annoying?

For AS projects, Flash assets are typically loaded by using 'Embed' metatags, using 'getDefinitionByName' or using something like Grant Skinner's FlashLib. I recently found out about an alternative method via a comment on Ian Lobb's blog, which is to use SWCs.

It turns out that using SWCs solves the above issues for very little extra setup. Using SWCs means the compiler knows about the FLA and gives code completion on symbol names and sub-clips. Anytime the compiler knows about stuff, it's going to save you debugging time by flagging errors before they happen. Symbols also retain their timeline ActionScript (unlike using Embed tags).

Example usage:

Example Flex Builder code completion:

Where this technique gets really interesting is with Flash Builder 4's Package Explorer. This allows you to browse inside a SWC and view all exported symbols and sub-clips.

This technique can be used with any smart AS editor. The set-by-step for Flash Develop is here. For Flex Builder you want to do something like this:

1. In Flex Builder, create a new AS project.
2. In the project folder create a new FLA: 'assets/assets.fla'.
3. In the Flash publish settings, check 'Export SWC'.
4. Create a symbol in the FLA. Set the Linkage id to: 'assets.MySymbol'.
5. Publish the SWC.
6. In Flex Builder do Project -> Properties-> ActionScript Build Path -> Library Path -> Add SWC. Enter the path to the SWC ('assets/assets.swc') .
7. In Flex Builder, edit the main class. Type 'import assets.'. The symbol name you defined in the FLA will now show as a code completion option.

Anyone know of any disadvantages of using this method?

The solution turned out to be simple. Copy all the library symbols from the damaged FLA into a new document. Error goes away. As far as we could tell, this was caused by sharing files between Flash version 10 and 10.0.2. Moral of the story - get the Flash update now.

which is a lot less code than:

TweenLite seems to have quickly become something of a Flash standard. It's a great library that is well maintained and just works.

The fix is to use a mini pre-preloader as supplied in the SWFAddress samples ('samples/cs3/c.fla'). The mini-loader is loaded twice but since it's so small it doesn't matter. I'm adding this information here since the issue is pretty buried in the SWFAddress forum.

[UPDATE] OK, another SWFAddress gotcha by virtue of obscurity: If your back button is not working, check you have specified the 'id' attribute in the swfobject.embedSWF() call. The 'id' attribute can be any string.

swfobject.embedSWF('c.swf?path=main.swf', 'flashContent', '100%', '100%', '9.0.45', null, {}, {}, {id: 'myId'});

I just found out that there is a new 'Battle of the Planets'/G-Force/Gatchaman movie coming out!

I used to love BOTP as a kid in the 80s. The weirdness and the beautiful animation really made it stand out from the typical U.S. cartoon dross. It was only later that I found out the original Japanese version (Gatchaman) was a lot stranger and more violent.

It’s interesting that even though the show was butchered for the western market, the original spirit shone through. I wonder if as western kids we would have been able to handle the original version, or if we needed the sugar coating of more linear plot-lines, Casey Kasem and 7-Zark-7.