6 for PSP, 9 for Mac & PC
A couple quick notes of interest regarding the Flash player:
Flash on PSP: Sony has announced that tomorrow they will release PSP Firmware Update 2.70 for Japanese-market units, which will include Flash Player 6. Someone translated a disclaimer that “a part of the functions is not supported” — we’ll soon see what this means. In the past, Japanese updates have functioned just fine on US units so we’ll let you know tomorrow! Anything you want us to test for you? Post the links in the comments.
UPDATE (April 25) — the new firmware showed up in “Network Update” on our US model PSP this morning. Downloading and testing now; will post more soon.
The Player Formerly Known as 8.5: When Beta 3 of the next Flash player is released, it will be called version 9 instead of 8.5. (Sadly, we thought of the Prince joke before we read Emmy’s post.) A major version number increase certainly makes sense given the AS3 capabilities of the player (in fact we’re kind of surprised they didn’t call it IX — roman numerals are cool!) The other numbering scheme was probably intended to avoid falling out of sync with the IDE; Emmy’s FAQ clarifies the release schedule.
If you’ve been watching your web logs you’ve suspected this change for a while:

…and it’s also evident that after 9, they’ll be starting over with 1. (But seriously: if you’re the person who visits this site with Flash Player 1 let us know; you might have won… something!)

April 24th, 2006 at 9:37 am
The player will get adopted before the authoring tool comes out, this is a good thing.
April 24th, 2006 at 9:38 am
P.S.> PSP missing something(s)? I’d think it’s either a sandbox security thing, or FScommand(s). Other than that, not sure what’d be harmful to the PSP CPU/Mem. Thoughts?
April 24th, 2006 at 10:19 am
I agree with you about the player beating the IDE to market: a good thing! Especially if Flex 2 leaves beta before the Flash 9 IDE comes out…
I’m worried about CPU/memory limitations in the PSP Player as well, especially as it seems it will be running in the browser, which already errors out on pages with lots of images and/or JavaScript. Hope this will be really functional and not too limited. We’ll see!