Monday, April 20, 2009

Flash at the BBC

The BBC are currently recruiting for contract Flash developers in various departments.

You will need to be a very good developer with great knowledge of AVM1 ;) But don't let that put you off, quite seriously some of the work at the BBC at the moment is in the realms of dream projects. If you fancy playing a part in the future of mainstream entertainment, where the user is not sat in front of a desktop computer then please forward a CV.

What makes a project quite often are the people. The people you'd be working with on a day to day basis are legends in their field so the opportunity is second to none.

All roles are based in the UK, however international applications are not out of the question if your English is near fluent and you don't mind living in the UK for a bit.

Send me an email at

Labels: , ,

Tuesday, March 24, 2009

Why native accessors are really bad in Flash Lite.

At work we were discussing what standards we should use for coding. Things like consistency in formatting, naming and having agreed ways of doing things obviously makes everything easier.

So we entered into the discussion of public variables versus native accessors versus custom functions. Here's what I mean when I refer to the different accessors:

native accessor:
public function get width():Numbe{return _width;};
public function set width(value:Number):Void{_width = value;};

public variable:
public var width:Number;

private variable:
private var width:Number;

custom accessor function:

public function getWidth():Number{return _width;};
public function setWidth(value:Number):Void{_width = value;};

The most compelling argument to use custom accessor functions is that public/private variables, and to a lesser extent native accessors, don't allow you to hide your implementation. This is fine and good, but we are using Flash Lite with a resource limited device. In this scenario best coding practice sometimes has to make way for best performance.

So we decided to do some tests to see what the overhead would be of accessing variables one way or another?

Speed Test results in ms, making 10000 gets and sets:

Custom function 2439
Public variable 2394
Private variable 2395
Native accessor 13450

Memory Test results for creating 10000 instances of each class (kb).

Custom function 6528
Public variable 6528
Private variable 6528
Native accessor 6532

In terms of memory, everything is exactly the same except for native accessors.

For performance, the results show that public/private variables were very slightly faster to access compared to custom functions. However, the massive suprise is that native accessors are more than 5 times slower than public/private variables or custom functions. This is truly shocking, and really could completely slow down your application if you used them extensively.

So in many ways our decision about what approach to take with accessors was made really easy; never, ever, use native accessors! The marginal difference between public/private variables and custom variables was deemed insignificant when compared with the benefits of hiding the implementation.

It is possible to justify the use of public variables in some cases. If you have a value object that is strictly read only and has no functionality, then there is nothing to hide in terms of implementation. The only difficulty here is how do you determine that a value object is read only? How do you guarantee that it will never have any functionality going forward?

Labels: ,

Tuesday, July 01, 2008

Opera Mobile and Flash

Seems like Opera for mobile is now actually integrating some form of Flash within the browser. There was some tentative announcement back at the MWC that it would support Flash Lite 3, I guess this is the first step.

I think what Opera do is just hook into whatever 'player' is present on the device, so they implement a standard api. However, that can only really lead to a pretty fragmented implementation. Also not sure why its even worth implementing Flash Lite 2.1, flash player 7 is understandable for the video.

My first test with a Nokia N95 8Gb crashed the browser when it tried to access Flash content, but to be fair that has Flash Lite 3 which isn't listed in the tech spec- interesting to see if it works on any Flash video content (Flash 7 is listed as supported - I pressume for windows mobile).

Labels: ,

Thursday, March 29, 2007

dealing with fscommand launch

If you've ever wanted to use Flash Lite to communicate with C++ then fscommand("Launch",application) is a very useful feature. Its purpose is to allow you to launch an application on the phone and pass in addional command line parameters if necessary. So you could for example launch the browser and pass in a web address. Thats a basic example and there are other ways of doing that with getURL(). The real value in the launch fscommand is that it allows you to launch your own C++ application in the background to support your Flash Lite application.

In a recent Flash Lite project where we needed to use fscommand("Launch",app)
we came up against a few issues when it came to s60 3rd edition phones. So heres a summary of things to consider when using fscommand("launch").

You will probably have to call fscommand("launch") from a button press as it needs to be a user initiated action.

For 3rd Edition phones, because of the way applications are accessed you do not give an actual path to the application. So if I wanted to open the browser I would just do the following:

fscommand("Launch", "browser.exe");

For 2nd Edition phones you have to give the full path to the executable file. So for example:

fscommand("launch", "z:\\system\\apps\\browser\\");

Passing in arguments works the same across s60 3rd and 2nd edtion devices by putting the arguments after the application. eg.

For 2nd edition: fscommand("launch", "z:\\system\\apps\\browser\\,");

For 3rd edition: fscommand("launch", "browser.exe,");

However we were unable to read the arguments for our custom application. So it maybe that because of the security of the 3rd edition only the native applications such as browser can accept incoming arguments?

When it comes 2 way communication between Flash Lite and other applications the more effective way to do this is by running a local server on the device and then using loadVariables or even XMLsocket to talk to the native app. Although theres no point having a local server listen out for FL calls if FL isn't even running. So fscommand is again crucial here as a the starting point of communication.

Labels: , ,

Friday, November 10, 2006

Flash Lite 2.1 for free

We'll this was probably the most asked for and argued over issue with Macromedia's Mobile policy. Finally the Adobe Flash Lite player will be available to developers without a price tag. That should bring the Flash Lite forum traffic down a bit :)

Further still - the 2.1 player will be available to END USERS for free if they already have Flash Lite on their phone. So that means you can point users with 3rd edition phones to the Adobe site to get the 2.1 player before they consume your content :)

This was an essential move I think because the mobile market place is hotting up (competition wise) and 1.1 just doesnt cut it. Waiting another 18 months for 2.1 to make it out there would have been very painful. Thank you Adobe.

Read the release here

Labels: , ,

Wednesday, November 01, 2006

cell and shockwave link up

A few posts back I talked about the possible influx of content from Japan. So it was interesting to read via wirelesswatch that Cell have signed a distribution seal with who also funnily enough have a deal with Verizon for their Flash Lite based 'Shockwave Minis' arcade! In fact some of Cell's games are already part of the arcade, and you can play them here.

I think there are a couple of things that are actually bad about this though. Above all the Brew platform supports Flash Lite 2.1 and is capable of so much more than 1.1 based games built for in browser experiences. One button games have their place but its pretty limited. Flash Lite will be a lot more than that on the Brew platform as developers start to develop original games specifically for 2.1 not throwing existing content into the mix because its easy to do.

Labels: , ,

Thursday, October 26, 2006

Symbian Smartphone Show Application

For anyone who couldn't make it to the show and missed the Flash Lite based Symbian Smartphone Show 2006 guide we (Flash Cell) built for Symbian.

Now that the show is over the Symbian website will probably stop offering it as a download, so if anyone is interested in downloading it you can get it here. There are 3 different versions, s40, s60 3rd edition and also s60 2nd edition. The 2nd edition version is the Teleca powered Flash Lite solution, which maybe of interest in light of the recent Teleca and Adobe announcement.

Labels: , ,

Thursday, October 19, 2006

Symbian Smartphone show round up

So the SPS has come to end. I was down there on both days for a few hours to checkout the general buzz. Its not a massive show, but a very focused one and its always good to check out the latest devices. I managed to get my hands on the Samsung SGH i520 which is running the s60 3rd edtion FP1 and includes Flash Lite 2.0, so I bluetoothed across a few FL2 swfs to checkout the performance - seems pretty good. There was also an LG phone powered by the new s60 platform, great to see Nokia's implementation of Flash Lite going beyond Nokia! What happened to the LG licensing deal and the rollout of Flash Lite phones I wonder?

There was quite a lot of promotion of the new s60 fp1 as you'd expect, including bits of documentation about Flash Lite 2.0 on the Forum Nokia stand. In all there was a definately a more visible presence for Flash Lite from the previous year. People actually know what you are referring to these days when you say Flash Lite, rather than it being interpreted as the camera flash light :)

It was also good to see a few other Flash people there too.

Labels: , ,

Saturday, September 23, 2006

Duck ... Flash Lite content coming this way from Japan

Just listened to an intersting podcast about a Japanese Flash Lite content company called Cell who were at CTIA showcasing their games catalogue of over 400! The guy being interviewed was obviously well versed in mobile conferences outside of Japan because one of the first things he asks the interviewer is "Do you know Flash Lite?" The interviewer resonds "yeah ....Flash based games right?" So clearly the interviewer doesn't know Flash Lite .... such a classic opening to a conversation about Flash Lite, I have lost count of the amount of times I have experienced that opening sequence :)

So whats interesting about all this is that while many early adopters of Flash Lite outside of Japan have looked on with envy at the market penetration of Flash Lite over there, content producers in Japan have just been building away. Not only does the Japanese market offer a great market base, the performance of Flash Lite on the handsets is also way superior - 30 fps is not a problem.

So the success of Flash Lite in Japan is unquestionable and the net result of that is that there are lots of good sized content creation and distribution companies who specialise almost exclusively in Flash Lite. But the market is now totally saturated. Recently when I spoke to a top distributor in Japan they told me they were only interested in 3g content as opposed to 2.5g and that translated as music and manga, not wallpapers, screensavers or games!

I guess it comes as no surprise then that companies with lots of assets and production power will start to look outside Japan. Cell say they have 400+ games and a production line that produces 12 games a week. Now, these are obviously pretty impressive figures even for the casual genre that Flash Lite fits into. However the key question I think for Japanese content creators looking overseas is what percentage of their catalogue is culturally exportable. Porting their content to English version should be easy enough but will consumers 'get' a lot of the content the way Japanese consumers have?

One of the reasons Cell have 400+ games is because Flash Lite content is quick to build and quick and easy to consume. Also dont forget that Flash Lite games in Japan are entirely browser based. So in the interview when they say 200,000 downloads a day I would guess thats actually 200000 hits per day. Of course you can save browser games locally but the point should be made the consumption model is so much more appetising and free flowing when compared to games consumption in Europe or elsewhere.

So the key point to all this is that Japanese content providers face the same big hurdle that Western content providers do when trying to get into Japan - there are massive cultural differences. I think is so much more relevant to Flash Lite than other technologies because its such an expressive technology and the content is so low brow (almost viral like - see internet viral campaigns) that it absorbs a lot of cultural influence. So take the example of Playstation games - these are big budget games that feed off raw gamer needs, no frills, they are not culturally influenced. A lot of Flash Lite content has a cultural context.

I look forward to seeing how well Japanese content providers do in shifting content in the newer markets! If they select the right products, there are still a few significant technological differences between Japan and non-Japan in Flash Lite implementation. Only titles that can work with less processing power, can adapt or justify the different input methods, can find a identity graphically and have a cultural context will make it. See one such example below.

Labels: , ,

Friday, June 16, 2006

Flash Lite Friday Digest #10

Its FlashLite Friday Digest time again, and this week I have the honour to write FlashLite Friday Digest No. 10. Its several weeks since the last digest and lots has been happening in the Flash Lite world.

The biggest news of the digest has to be the announcement and presentation of Flash Lite 2.1 for BREW at the Brew 2006 conference. The basic info is that Flash Lite 2.1 for BREW will be out on a public beta on the 3rd of July and later in the summer developers will be able to distribute their content based on the Flash Lite 2.1 profile through Verizon. There are 2 really nice improvements in Flash Lite 2.1 - xml sockets and inline text. These 2 key features make FL 2.1 a much more capable competitor of other mobile technologies.

See the Adobe Brew developer center for more info!

The videos from the conference are also available online now, see Bill's blog for the links

The Flash IDE received its 3rd device profile update this month so be sure to download all the new devices from here

Flash Lite instructor training has been announced for the US, its a 3 day course and is free! More info here

There have been some nice new phones shipping in the last few weeks too. Most noticeably the new Nokia series 40 phones are now available Nokia 6125, 6131 and 6234 (vodafone exclusive). Also a few new Sony Ericsson phones that *should* support Flash Lite : W300, M600, W700i. The M600 is particularly interesting because its the first Symbian UIQ 3 phone to be released by Sony Ericsson and the first UIQ phone that has Flash Lite pre-installed. NB .Information based on Sony Ericsson website.

Nokia released a new theme studio 2.1 for series 40 phones. It allows swfs to be part of a s40 theme and integrated into wallpapers, screensavers and possibly more UI elements. I haven't had the chance to check it out yet and the documentation isn't 100% clear on where you can and can't use swfs. (via: bemobil).

Nokia have been very active over the last month in engaging with Flash Lite and have produced the kind of documents developers really need to see. Last month they released the Flash Lite Visual Guide as well as the Flash Lite global ecosystem documentation. A few days ago they announced a whole new Forum Nokia section called Forum Nokia Blogs and have a dedicated Flash tag.

In the world of the Adobe website there are a few new developer articles available:

Converting Flash Content to Flash Lite 1.1 Jae Young Chae (May 30, 2006)

Tips for Developing Flash Games for the iRiver U10 Sung-Hee Park (June 5, 2006)

Creating iRiver U10 Games for Beginners Eung Kim (June 12, 2006)

Also Mike has an upcoming seminar this wednesday (June 21, 2006 4:00 PM - 5:00 PM US/Eastern) about the Flash Lite 2.0 media playback API, be sure to register your interest here

If you you never made it to the Flash Mobile Day, as is the case for most of us, then you'll be pleased to see that the presentations are now available online here.(via: biskero).

That's about all the major Flash Lite news there is! The archive of FlashLite Friday Digest can be found here :

Labels: ,

Wednesday, June 14, 2006

Forum Nokia Flash blogs

Slightly old news but worth bookmarking.

Flash Blogs

I think it will also be an interesting read as some of the bloggers are traditional mobile people starting to get involved with Flash Lite. Most of the Flash Lite industry at the moment are Flash developers and designers moving across to mobile. Quite a difference!

Labels: ,

Friday, June 09, 2006

My N80

I have been using my N80 for just over a month now and thought I'd post a few thoughts on what I like, and also a few angles on Flash Lite. The first thing that I am still getting over, is how good the screen is, there can only be room for QVGA and better screens in the future. It really makes applications so much more attractive, from native phone apps, websites, to Flash Lite content - everything looks so much better. From a content production point of view there are things you can do in Flash that take advantge of the high res that would not look so good in lower resolutions. For example, on low res screens small icons look better as bitmaps, however because of the extra pixels kicking around QVGA+ screens you can pretty much go with vector for even the smallest icons.

I am also really enjoying the new browser and life blog. I'll post more about life blog soon as I think it really does add lots of value to mobile phone users.

The Video and camera are now good enough to take photos/videos that are worth keeping. I have found myself using the video a lot more than the actual camera. The camera is good for certain photos, landscapes and close ups, and anything where the subject isnt moving! But I find the video great for just ad hoc snapshots on daily life. The quality is good enough to view on a computer or on a phone, and FPS is not too bad either.

The whole OS itself is really a nice refreshing improvement on previous versions. For example applications like the image and video gallery have a nice carousel style UI which makes browsing through items quite good fun. However the gallery does get polluted by Flash files! This is actually a really bad flaw because you cant preview Flash files and a lot of applications use multiple files to construct one application. So take for example the superb World Cup Flash application by Alen. This is installed, with all supporting swf files into the Flash directory (56 files in total). So the gallery picks up all these files which completely kills the usability of the gallery app. I guess this is a combination of Flash not fitting too well into a content type as well as developers needing to be aware of this and putting the actual content assets somewhere hidden!

In all I think it will take months to get fully up to speed on the full feature set of Series 60 3rd edition.

Thoroughly enjoying it so far!

Labels: ,

Tuesday, April 11, 2006

debugging Flash Lite

This probably just comes under the Tip of the Day category rather than any detailed info on debugging in Flash Lite. Basically in Flash Lite because the actual device player is used in the IDE it means that the debugger doesn't work. So what can you do when occasionally standard traces and error messages don't provide enough information?

There are 2 methods I use. Firstly to get a general picture of where the problem lies you can change the publish version to Flash 5+ and use the debugger in the IDE. This is useful for checking for any undefined variables and allows you to use breakpoints to walk through code as it executes.

The second method I use which is particularly useful for getting a quick reference to any object or method calls that simply don't exist is to use the __resolve function. The __resolve function is a generic function that gets called whenever you reference a non-existant method or object. So for example, in Flash Lite sometimes the IDE will report: 'Problem with content 5: - Actionscript Processing'. If you change the publish settings to 6+ and then define the __resolve method of the Object prototype you can get the name of the non-existant method or object.

Object.prototype.__resolve = function(arg) {

There are plenty of other production techniques you can employ, especially for Flash Lite 2.0 development that make debugging a one click process, but I'll have to save those for a later date :)


Thursday, March 02, 2006

Flash Lite and Sony Ericsson

So recently over the last few weeks Sony Ericsson have announced a whole new range of phones. Some really nice ones too with some relatively unique designs. In the past I have been pretty keen to state how great it is to see Sony Ericsson phones with Flash Lite embedded. You would think that one of the most stylish mobile phone manufacturers combined with Flash Lite would be an awesome setup for some really cool content to be created. Well - to be blatant its the complete opposite.

Sony Ericsson have had some issues with the performance of the Flash Lite player on their handsets - this is true. But this is not the reason nobody creates Flash Lite content for Sony Ericsson phones. Heres a few reasons why Flash Lite is failing with SE:

First up there is no communication between Flash Lite developers and SE. Sure there is a lot of protection of information in the mobile OEM sphere but there are plenty of developers out that who have a really good understanding of how Flash Lite can be used to great effect within the SE setup.

Secondly there is no technical documentation on Flash Lite or ANY developer information. This gives absolutely no confidence that Flash Lite is actually a technology that is intended to be used.

Phone specification on the SE website is not always accurate. How do you begin to plan to target a phone if you know that well, it may say Flash Lite on the website but it wont have Flash Lite really.

Firmware upgrades have removed Flash Lite. I am only aware of this being happening with the W800 but the mere fact that it has happened once is enough to further fragment and destroy confidence.

There is no consistency in the actual implementation of Flash Lite. So from the W550 onwards Flash Lite is used for browser and UI only. The use of Wallpapers and Screensavers is disabled. Is this documented anywhere? Nope. Given the wide variety of Flash Lite developers out there fragmentation of functionality is not a big issue in itself but zero documentation is a massive issue.

I think I could probably go on and explain a few more areas that are key reasons why Flash Lite hasn't been taken advantage of on SE phones. But you get the picture :)

So what does the future hold for SE and Flash Lite. The website lists some 6 new 'coming soon' phones that have Flash Lite capabilities. I am not so sure that all those phones will actually have Flash Lite pre-installed. Especially all the UIQ phones. SE could make a real niche with Flash Lite and UIQ using the stand alone player.

More long term I think the Nokia implementation of Flash Lite will probably cause SE to rethink what they could really do with Flash Lite. I don't know why SE Flash Lite is where it is but I would guess that its because SE doesnt really understand how to address the massive pool of Flash Lite developers or how to classify Flash Lite. I don't think Nokia will make the same mistake and the newer licensees such as BenQ Siemens look like they will be taking full advantage of FL too.

Labels: ,

Wednesday, January 18, 2006

Nokia Series 60 3rd edition SDK released

Yesterday Nokia released the SDK for the new Series 60 3rd edition. Why is this good news for Flash Lite people? Well Flash Lite is a part of the SDK. It comes as a plug-in to the browser as well as a standalone player. This should be exactly how the Flash Lite implementation appears on the actual series 60 3rd edition phones, such as the N91, which should be released this month. If you install the SDK you can see exactly how the browser will work, you can load remote swfs, save them to the Flash Lite folder, etc

Great to see it finally in action.

Labels: ,

Thursday, October 13, 2005

Flash Lite down under

Via wireless watch : NEC Australia has announced the launch of their first i-mode 3G mobile phone - the NEC N600i ...Available now in Telstra stores...

It would appear from a look at the product manual that swf playback is supported as an imode feature. More than likely this means Flash Lite 1.1 is supported. This will be of welcome news to a few of the Flash Lite developers I know in that part of the world!

Its also I good indication that as 'overseas' i-mode service providers move their handsets to 3G capabilities there is more likelihood that we will start seeing more Flash Lite 1.1 support.


Friday, August 12, 2005

Sony Ericsson w800i joins the ranks

When this phone was first announced I was really disappointed to read the specs on the SE website and see that it didnt mention Flash Lite as a feature. It really is a nice phone and what better excuse to buy one than for development purposes.

The w800i is the first in the line of 'walkman' marketed mobile phones. I comes with a 512mb Memory Stick and has been hyped up over here in the UK like no other phone before it. Even to the extent that no one was allowed to sell it until today (12th August). It had its own psuedo launch party at 00 hrs today (or rather last night), accompanied by Jay Kay selling and signing some of the first Walkman™ phones sold at the Oxford Street Carphone Warehouse in London.

Well as fortune would have it, in this case at least, the SE specifications arent always that accurate. After a few investigations it turns out it does indeed have Flash Lite 1.1 installed. So loaded with a good excuse off I went to buy one.

It supports Flash Lite 1.1 as per most other SE devices in browser, screensaver and wallpaper modes. And unlike previous implementations by SE, with this version you can send a swf as a MMS message and receive and view in the message pane itself!

Having played around with it for a couple of hours I can see how this type of device can habour a really well defined market for Flash Lite developers. Its clearly aimed at music loving stylish people. The buttons, the design and subtle features make it a really interesting brand of phone. SE will make a big splash with the walkman line of phones. 10/10

launch video (bbc report)


Labels: ,

Thursday, July 28, 2005

vodafone kk announces 2 new 3g handsets

Vodafone kk, which is the Japanese side of Vodafone's global empire, have announced 2 new 3g handsets, the Sharp 703SH and the Sharp 903SH. The highlight is probably the 3.2 megapixel camera on the Sharp 903sh. Both models are, as the model names suggest, the next generation of the Sharp 802 and the Sharp 902.

Having a Sharp 902 myself I cant imagine how good the screen will be on the 903, the 902 is by far the best looking screen I have seen. Add to that the 3.2 megapixel camera and it all adds up to a pretty high spec imaging phone.

Flash Lite is of course supported in both models too. Although no information was given about their availablity outside Japan, its very likely they will be available sometime soon in Europe.

see the full press release here

Labels: , ,

Monday, July 04, 2005

v600i and k600i released

Sony Ericsson's latest (Flash Lite enabled) 3g phones are now available. The v600 is available exclusively through Vodafone now and the k600i through other service providers including Orange imminently. I have opted to wait for the k600i as I actually prefer the silver finish and style. Expect a review shortly.

Labels: ,

Tuesday, June 21, 2005

iRiver U10 supports Flash Lite 1.1

via engaget, this link summarises a few of the new features of the new U10 revealed yesterday. Included in the list is Flash Lite 1.1. Although I havent found any official documentation it seems pretty genuine. This would be the first non-phone based deployment of Flash Lite 1.1. A lot of other devices use Flash but as far as I know they use the standard SDK to implement their Flash Player. Whereas this would appear to just use Flash Lite 1.1 off the shelf. Will be interesting to see how Flash Lite is intended to be used on this device. If its not a phone then it must have a least some kind of conectivity like wifi? If there is no connectivity then why would it have Flash Lite? How would people get Flash Lite content onto the device? Needless to say I will have to get one to findout!


Casio's G-Zone Type R

great site, even better phone

Of course the phone comes with Flash Lite pre-installed too

Labels: ,

Tuesday, June 14, 2005

Nokia's with Flash Lite pre-installed?

Since Nokia's February licensing aggreement with Macromedia for the Flash Lite platform Flash Mobile Developers have been eagerly awaiting the first deployment of the Flash Lite player on a Nokia phone. Although Flash Lite works on any series 60 phone it hasnt been made available to consumers via download or developers for distribution. This is a somewhat frustrating situation as there millions of series 60 phones on the market but there is currently no way of commercialising Flash based content for them. There is no info on whether this is a temporary situation or a policy that has been decided upon for the Flash/Nokia roadmap. I am inclined to think that its just easier for Nokia to have the benchmark for Flash as being Series 60 3rd Edition. At least that way its a straightforward way of defining a market for Flash on Nokia phones. Its also a good reason for consumers to want to upgrade to the all sing and dancing next generation Nokias. From a developer point of view it slows the production of content. If the series 60 platform was targetable by bundling the Flash Lite player in a sis or by allowing consumers to download it in much the same way as real player is offered to ngage users then that would enable the comercialisation of content now! But as things currently stand there is no market and therefore no justifiable reason to dedicate resources to Flash lite. Of course I am sure many companies are producing content as part of a long term strategy, but I mean more the push for companies to commercialise existing assets now.

So assuming things stay as they are Flash developers are looking forward to the first series 60 3rd edition phone to be announced that can offer timestamp for the rollout of Flash Lite enabled Nokia devices. This however seems to be a confusing process. The latest series 60 phones (the n-series)were announced recently and I was hopeful that they would be series 60 3rd edition phones but alas initially the documentation pointed to the 2nd edition. However, a bit further down the line it appears that the N91 will be series 60 3rd edition and will therefore be the first series 60 Flash Lite enabled phone. How confusing is this?

To confuse matters further the register recently posted an article on the new series 40 phones recently announced by Nokia. Among the details they stated that the phones supported the newly announced series 40 3rd edition which in turn supported Flash Lite. So we will have to see if this is true in the next few weeks as Nokia unveil more information about the series 40 3rd edition. I have been unable to verify whether the series 40 3rd edition actually does support Flash Lite because there is limited documentation at the moment.

So there we have it, the Flash Mobile community can definately smell the first Nokias , they are on their way. What remains to be seen is what models first ship and in what form the Flash Lite player has been implemented. The existing player runs as standalone rather than browser which is great for applications. However from a commercial point of view would Nokia really ignore the selling power of having Flash Lite available for standby and wallpaper? Is the Japanese model really so different from what non-Japanese consumers want? I dont think so. Sony Ericsson seem to see the Japanese model too, where Flash Lite is some sort of advanced dynamic eye candy. I think if Nokia were to add the sceensaver, wallpaper and standalone implementation of the Flash Lite player then it would really be a great platform for delivering both eye candy and applications to Nokia users. If they just opt for the standalone implementation then it will still be great for fun as well as serious applications but will miss the opportunity to progress beyond the stayed era of animated gifs.

Labels: ,

lots more Sony Ericsson phones

The next batch of Sony Ericsson phones have been announced and once again there are a few models supporting Flash Lite 1.1.

In order, from left to right, the k608i,v600,w600 and s600i all support Flash Lite 1.1.

The k608i and the v600 are variants of the 3g k600 annouced a few months back. The v600 is a Vodafone exclusive, much the same as the v800 was. And the k608i is rumored to be an exclusive for another operator - possibly for Three? With the above addition to the Vodafone portfolio it means that 3 of Voda's 7 3g handsets will come with Flash Lite pre-installed. Of the other 4 handsets, both the series 60 Nokias support Flash Lite but dont have it pre-installed.

The other two SE phones (w600 and s600) are operator independent phones, at least that seems to be the case.

Labels: ,

Monday, April 11, 2005

Sharp 902SH

I really do love this phone. Its screen is just great, it looks way better than any other mobile I have ever seen. The camera, at 2MP, means that you can get some really good quality photos. In fact my aging Sony camera, at 2MP, has just been rendered useless.

I also like the way the box has not 1 but 2 Macromedia logos on it: (taken with the 902)902_box

It has loads of other great features, including bar code scanner. So I can scan those Japanese square barcodes (QR Codes I think they are called) on a website and get the link on my phone. I can also create my own QR codes, heres a link to this site :)

The only annoying side to it is the bluetooth receiving process. If you use bluetooth a lot this really does get annoying:

calling not available during operation, OK? (yes)

Enter Handset Code: **** (ok)

received (ok)

save to pictures (yes)

saved to pictures (ok)

connection terminated (ok)

Regardless it is a great phone, and having Flash Lite available as screensaver, wallpaper and browser is really cool.

Labels: , ,

Sunday, April 10, 2005

Sony Ericsson to deliver Flash Lite

It looks like the above handsets will have Flash Lite pre-installed which makes them the first real set of operator independent Flash Lite phones. Flash Lite is mentioned in the developer world white papers for the k600i. I am pretty sure that the z800i will include Flash Lite as it is essentially the v800 with SE software rather than Vodafone branding.

Anyway you look at it this is great news for Flash Lite developers. In addition they look like really great phones, even if I cant afford to buy them all just yet :)

Heres a snippet from the k600i spec:

The Macromedia Flash Lite player is pre-installed in
the phone, allowing users to take advantage of the
features of Flash images. Flash images can be
embedded as moving objects on a Web page or
they can be available as stand-alone Web pages. It
is possible to interact with flash images using the
navigation key. Flash images can be included in
picture messages.

NOTE - I had mentioned the k750 and the d750 in this post but I have since learned that the whitepaper specified Flash in error. Unfortunately the k750i and the d750 do NOT support Flash Lite.

Labels: ,