Adobe's Flash Player 10 for Android is going to be shown/announced in October.

For most people, this is not even a big deal. However for myself, an Adobe Flash/Flex developer, this is huge to me. I totally enjoy whipping out my Nokia N810 and showing my work off to clients. But with Adobe Flash Builder 4, formerly Flex Builder, coming out and it's pushing me to Flash Player 10, my Nokia N810 isn't going to cut it.

However, I wonder if Nokia Symbian is open to letting FP10 run in the lower layers of the OS/API, is Maemo?

Out of curiosity, why is Flash Builder 4 going to push you to FP10? Can't you tell it to compile for FP9 instead of the latest and greatest?

This is actually something I've wondered about for some time. It seems that immediately after a new version of Flash Player is released, all new flash apps require the latest version, regardless of whether or not they're actually using any new features. Does Adobe purposefully make it difficult to develop for the old player?

No, it's pretty easy to develop for older players (I had to do it daily at my old job because of slow IT adoption policies: IE6 and Flash 8 up until just recently). But, developers like staying on the bleeding edge and like using all of the new widgets and gizmos (e.g., Flash 10 supports 3D, inverse kinematics, new keyframing tools, etc. and the older versions don't).

Tim

As it stands, the Flash Builder 4 beta pushes you to FP10 since the xmlns for Flash Builder is newer and supports only FP10 at the moment. Flex Builder 3 supported downgrading in some areas to FP8, but mostly you'd just stick to FP9 since it would guarantee less issues on compile.

If you're using the Flash IDE, you have the ability to push out to FP10 and down a tad bit easier. The main difference though is that if you tried to push out certain video types - On2 encoded instead of Sorenson encoded, you're likely to run into some issues with your FLV version if you go down too far in version(s).

There are other reasons to stick to the default of Flex Builder - I ran into a very nasty issue where I couldn't trace/debug/profile any PureMVC based Flex projects in the current build of Flex Builder the moment I dropped below FP9. So far, Flash Builder 4 is pushing for FP10, I'll just drag my clients to that platform since I can usually find a good reason to go there.

Mainly, it's for debugging that I push ahead. They break that, and I'm ticked because I'm being forced. And that's what I'm noticing right now. And for the record, the inverse-kinematics, et al are part of the Flash CS4 libs, not Flex. The 3D portions are FP10 specific, but I tend to use Papervision3D or Away3D - lately Five3D - instead since I can degrade to FP9/8 if need be and not cut my clients off due to their limitations.

But if I have to use PureMVC, SWFAddress, and the like... I'm sticking to FP9 in the current build of Flex.

can you please put a link to download fp10 on android please ......

October during Adobe MAX. It's only June

Every Maemo developer has access to all the "lower layers of the OS/API" that Nokia do, so the openness bit isn't really relevant as to whether Flash 10 will appear for Maemo.

Makes sense, just odd that no updates for the FP 9 has arrived quite yet. But it does seem like Open Screen Project will fix all of that. But will it show up in OS 2008... or just Fremantle?

Which Maemo will get it? I'm personally stopping at Diablo. And demos like the HTC Hero with FP 10 are enticing to other OS's.