Comments on: The Bad Flash Experience Inside Facebook

By: Just Flashing - Today’s Top Blog Posts on Flash - Powered by SocialRank

Just Flashing - Today’s Top Blog Posts on Flash - Powered by SocialRank — Mon, 01 Oct 2007 09:06:23 +0000

[...] The Bad Flash Experience Inside Facebook [...]

By: Scott

Scott — Wed, 12 Sep 2007 08:47:24 +0000

Damn, my example tag was stripped “Something like . ” should of read like so:

param name=”defaultVolume” value=”0″ <

By: Scott

Scott — Wed, 12 Sep 2007 08:45:32 +0000

I brought this up with the Flash Player team when we were discussing our wishlist for next gen flash players. It would be great if there was a paramater that accepted a boolean or better yet an int so you could set the default volume of your swf. This would allow sites like facebook to ensure that volume isn’t blaring when the user hits a site. Something like . I also brought up the fact it would be nice if there was a sound control api that could be accessed via js by default in the player, this would allow another way to set the volume by default. My 2 cents.

By: Darren

Darren — Tue, 07 Aug 2007 14:03:29 +0000

I agree with what FB are doing by not attacking the users with animations and adds, but if you install one of the applicaiton you should know what your in for, so i agree with loosing the click activate too.

By: arpit

arpit — Fri, 03 Aug 2007 01:39:04 +0000

heh, I think us Flash developers have it better than the javascript / ajax dudes. No Javascript allowed on the facebook homepage at all

By: arpit

arpit — Fri, 03 Aug 2007 01:38:49 +0000

heh, I think us Flash developers have it better than the javascript / ajax dudes. No Javascript allowed on the facebook homepage at all

By: Jesse Couch

Jesse Couch — Thu, 02 Aug 2007 21:38:02 +0000

Facebook did invent their own fbml for facebook developers to user when building facebook apps. This could be part of the solution for users own pages.

This is abit off topic, but have u noticed that when making a facebook application with flash(i.e. “.swf” that runs inside an iframe inside the facebook site). All the text input widgets malfunction with flash player 9.0.47.x

not all the key strokes are read into the text inputs. even when typing slowly.

By: Don Burnett

Don Burnett — Thu, 02 Aug 2007 03:20:19 +0000

Do we know the result of that patent lawsuit abut embedding multimedia in a webpage? Will that lttle click on content thing ever go away?

By: JulesLt

JulesLt — Thu, 02 Aug 2007 01:58:45 +0000

My guess is it’s something to do with keeping the page size down – i.e. the SWF not being downloaded until it’s clicked. MySpace is hell because the kids creating pages don’t understand that embedded a multi-MB photo-stream or some such causes the page to take an age to load. (Depends on what SWF they embed – many of the newer services are a lot better and presumably download a small SWF that then streams?)

By: Michael

Michael — Wed, 01 Aug 2007 22:47:50 +0000

Hans is right, it’s just on the profile pages. Forget the MySpace comparison, profile pages get tons of hits and Facebook optimizes around this. There are no iframes allowed on the profile. All of the FBML is cached, i.e. you have to persist the FBML to the user’s profile via one of the REST APIs. Everything is designed around making that page load super fast. No annoying slowness like on the Google personalized homepage, or Netvibes, or many people’s blogs, or for that matter, MySpace. They allow the fb:swf tag in the FBML for the profile, but they watch the HTTP traffic when you load the page. Your browser doesn’t load the SWF until people click on the image. So there’s no SWF download and (more importantly) there’s no SWF -> remote server traffic slowing down the initial load of the profile page.