« SXSW Twitter | Main | Video future at SXSW »

March 10, 2007

Java Micro, Flash Lite 3

Java Micro, Flash Lite 3: Michael Singer of InformationWeek writes of an Adobe Mobile presentation at last week's Game Developers Conference in San Francisco. There were apparently demos of web video running in Adobe Flash Lite 3. The article offers martial metaphors for Java, but I think these actually offer different types of value... Java Micro Edition (J2ME) is a to-the-metal programming language, while Flash Lite is an abstract services layer above different device types... you can do things in both. Direct programming can reach a lower range of device; sharing code cross-platform, cross-project works easier at the higher level. Development speed and common high-level functionality tend to become more important as time goes on. The video in Flash Lite 3 shows this -- Flash Lite 2 uses "device video", asking the current phone to use whatever codecs it has to play a matching video asset -- Flash Lite 3 promises to provide a common "Flash Video" layer across handhelds, and also across laptops. Cutting development costs while increasing audience size... that's the common ground behind a lot of Adobe initiatives these days. Related: A "Flash Lite vs J2ME" e-seminar later this month, with three developers telling what they see in the field. [via indiMad]

Update: Bill Perry, who presumably did the Adobe presentation at GDC, says in comments here that the following line in the original article is incorrect:

Information Week sez:

Adobe, which is working on version 3.0 of its lightweight Flash platform, was quick to show off the new version's video playback prowess and other features when working with Qualcomm's BREW format.

Adobe sez:

We (Adobe) did not show anyone Flash Lite 3 on any device last week at the Game Developer Conference in San Francisco.

Posted by JohnDowdell at March 10, 2007 09:06 AM

Trackback Pings

TrackBack URL for this entry:
http://weblogs.macromedia.com/mtadmin/mt-tb.cgi/8464

Comments

Hinkmond Wong has a good example of the current anti-Flash argument:

Here's an article that talks about Java ME technology versus Flash. Dude has a bias against Java ME though. He says "only works marginally" and you have to "write once, test many". What a weenie. "Wah, I have to actually do my job and test my code." MSA addresses fragmentation, and there are many working on the solution instead of being part of the problem. One thing's for sure, Flash is not the answer.

Some people prefer doing more coding to delivering completed projects, and don't mind increased testing and maintainence costs. Takes all kinds.

Posted by: John Dowdell at March 10, 2007 10:11 AM

I love Flash Lite and love the possibilities, but my one and only major gripe is the lack of interface with a phones main features Bluetooth, Camera and the Diary all of which I've seen accessed my j2me applications

[jd sez: True, device-specific coding does offer advantages too. Once a market developers for a particular device feature then it usually gets componentized, and jumps up into the service layer. But for a particular device with a new feature, low-level coding is usually the first way to access it.]

Posted by: cisnky at March 10, 2007 10:49 AM

The fundamental advantage of Flash on desktop was/is the fact of almost instantaneuos upgrade spread: from realease date to be installed in the vast majority of machines there is only a few months lag. This advantage is non existant in the mobile version, which, thanks to its non upgradability, promote heavy fragmentation of the installed user base, so when a developer want to use features of the newer version, his/her potential user base starts again from 0. Before you can think of deploying a service based on a new version you have to wait at least 18 months so there is a significant user base; by that time Adobe probably would have announced at least another two versions of FlashLite, trenching your expections again.
Also, it would be good to know what versions are actually comprised in the 150-200-250 Millions devices Adobe says have FL on-board. It is quite misleading the way they portrait as it looks like these devices all have the latest version of FL, while in fact it is heavily fragmented between 1.0-1.1-2.0-2.1. Another important datum missing is where these devices are actually located, if you plan to sell a service to Vodafone UK, they could not care less about these device being 70% in Japan or somewhere else.

Posted by: Endry Deloir at March 11, 2007 05:08 AM

Hi John. We (Adobe) did not show anyone Flash Lite 3 on any device last week at the Game Developer Conference in San Francisco. Please update your post to reflect this so the broader community doesn't think we showed Flash Lite 3. I've already contacted the original person (Mike) and asked him the same thing. Thanks.

[jd sez: The report got it wrong? Sheesh. Thanks for the heads-up -- I'll keep my eye on this and update this echo when they update the original. Thank goodness for comments....]

Posted by: Bill Perry at March 11, 2007 07:04 AM

i guess the much needed feature is add an API in FL to download & save content locally. i.e. imnages/additional swf/updated contens etc.

FlashCast offer this, but it diffirent implementation.

currently all my clients are asking for apps who can download and save upadted content locally to save data charges.

i hope abode will pick it. :P

// chall3ng3r //

Posted by: chall3ng3r at March 11, 2007 07:22 AM

"Also, it would be good to know what versions are actually comprised in the 150-200-250 Millions devices Adobe says have FL on-board."

Yeah, it would be good to know. I reckon 95% of that figure is Flash Lite 1.1

Posted by: cisnky at March 11, 2007 09:49 AM

Endry Deloir raises some solid points, although I suspect from a more pessimistic viewpoint than mine.

Yes, laptops have an "update your computer" dynamic which is not present on phones. This isn't unique to Flash Lite. Fortunately the hardware cycle is faster with mobile than laptops, but there isn't the "majority in six months" that we see with the regular Adobe Flash Player.

For stats, Adobe sez "X million device have Flash Lite installed", which is correct. This would be a mix of versions, and to my knowledge there are no publicly collected stats as each manufacturer ships the latest version, month by month. I would agree that predictions about your own particular audience may be only slightly informed by stats about the public at large.

I couldn't guess when the pocket scene would evolve enough to support manipulation of the local storage system.

jd/adobe

Posted by: John Dowdell at March 11, 2007 09:53 AM

Still this has a really nice ring to it. Now that I tasted AS3 I will not ever go back to AS2, even for mobile I'd rather wait to see if phones pick up the next lite version that is AS3 based.

And doing what Flash Video did to the web, doing that for mobile would be equally awesome. I can't wait.

Posted by: German Bauer at March 11, 2007 08:54 PM

Being able to write real apps with Flex and AS3 was an eye opener for me. Previous versions of flash didn't seem appropriate for application development. The whole movie analogy sucks. It was just too weird coming from a computer science background and having written many apps in C, C++, Java and PHP over the years.

When AS3 is supported on mobile devices I'll be porting my windows CE apps to swf and not look back. AS3 will be the Java that was promised but never delivered. Until then its still a toy IMHO.

Posted by: Igor D at May 18, 2007 07:17 AM

Post a comment




Remember Me?



(you may use HTML tags for style)