Flash Player Auto Updates - Where Are They?
Something i’ve been wanting to ask for a long time now is, why doesn’t the Flash Player auto update? When Moviestar is released, wouldn’t it be great if YouTube would be able to switch all of it’s users almost overnight? It seems to me that it should be a no brainer feature!
So what are the options?
1. Silent Update
This is a tricky one. On one hand you have a seamless user experience and on the other you have trust issues. I’m very much about users having seamless experiences, I think it’s the cornerstone of todays modern computing. So imagine if you will, Flash 10 has just been pushed to the masses and your able to start developing on the new version straight away, without your boss bring you back down to earth.
It sound like bliss to me. But let’s also imagine that the Flash Player was Real Networks, Microsoft or “Facebook App Company X” product. It’d just be a matter of time before we saw piggy-back middleware taking over our machines. As Flash developers, we need to know that our experiences are not going to be tainted over time.
But, we trust Adobe right? We have disabled keyboard access in fullscreen, cross-domain policies and whole bunch of other stuff that stops Flash developers running riot with a SWF. The player has an excellent history of backwards compatibility, thus I’m not fearful of updates breaking my favorite sites. The only thing the Flash player is infamous for is attracting a long list of bad developers who create poor experiences.
So maybe this isn’t a trust issue. Could it be in-fact a self-help mechanism for the Flash Player team; either make compelling improvements or else no one will choose to upgrade. If your guarantied that your user base will automatically receive your software, where’s the driving cog of your motivation?
2. Built in Express Install
Today the best way to make sure users upgrade is to use the Express Installation “hack”. I call it a “hack” because it’s ugly, super ugly. JavaScript, VBScript and a SWF Badge all get together and if the user clicks YES, the mission is successful. And to top it off, it’s up to the developer to implement all of this correctly. Can Adobe sleep at night? I know I can’t; even the new SHARE beta gives me the express install dialog even though I’m using the latest F9 player, what gives?
Why not build it into the Flash Player? Well, I’m kind of half hoping that it’s already been built into Flash 9, but I’m not holding my breath. So, let’s try and understand why Express Install wouldn’t be built in. Well for one, it’s a branded upgrade; the SWF badge can be skinned in anyway you wish. Also a site may have an alternative to there Flash experience that they would prefer a user visited instead of installing new software.
I think this is enough reason not to build in Express Install as it may take too much away from a brand, but on the other hand, why not let developers decide … stage.enableAutoUpgrade = true .. sound good?
I think I’ve gone on long enough to get my point over; we need a built in solution for upgrading users. Especially now that we have competition such as Silverlight biting at Flash’s heals. We know Microsoft won’t play fair. And as I recently found out, they are already pushing out FUD to people why they need to be using Silverlight. Please Adobe, act! What good is Quake II running in Flash if no once can view it for 12 months?
Comments(6)


