assertTrue is the professional blog of Luke Bayes and Ali Mills

Flash Lite Phone Recommendation

Posted by Ali Mills Wed, 21 Feb 2007 08:14:00 GMT

If you’re interested enough in Flash Lite to (like me) buy a phone to experiment on, I’ve got some recommendations for you. My recommendations are based on experience spent on two recently completed Flash Lite projects (one Flash Lite 1 and one Flash Lite 2) where I worked with over twenty different phone models during the past three months.

From a Flash Lite performance perspective, I recommend a Symbian S60 2nd Edition phone. The S60 2nd Edition phones consistently worked better for me than all others and never crashed. It’s funny. I’d think that if “2” is good then “3” would be better, but that’s not the case here. Flash Lite performs better on S60 2nd Edition than the S60 3rd Edition. I recommend the following phones in the following order based on Flash Lite performance:

  1. Symbian S60 2nd Edition phones
  2. Symbian S60 3nd Edition phones
  3. Symbian S40 phones
  4. Verizon Wireless supported handsets
  5. Windows Mobile 5.0 devices

From a money-making perspective, I recommend a Verizon Wireless supported handset. The LG Chocolate performs best, but supposedly more customers have a RAZR, so the RAZR gets the recommendation since we’re taking the money angle. You’ll have to jump though insane hoops just to get started testing your content (and even more to publish it), but Verizon undoubtedly has the best Flash ecosystem in the US. I recommend the following phones in the following order based on money-making potential in the US:

  1. Verizon Wireless supported handsets
  2. Symbian S60 2nd Edition phones
  3. Symbian S60 3nd Edition phones
  4. Symbian S40 phones
  5. Windows Mobile 5.0 devices I already mentioned why Verizon gets the top slot in the list above, but let me explain why the other phones are ordered the way they are. The Symbian phones get the next three slots because Handango provides a service to sell and distribute content for Nokia handsets. The S60 phones are first in the Symbian division because with with some custom work you can wrap the product with an installer and application icon (2nd Edition is above 3rd because SWF3SIS is available to build an installer with icon for S60 2nd Edition running Flash Lite 2.0 and earlier). Then come the Symbian S40 phones. These just barely made it above Windows Mobile 5.0 devices because I haven’t seen a way to make an installer and icon for them. Also, and more importantly, on S40 phones Flash Lite is treated as a second-class citizen. For example, on my Nokia 5300 SWFs are nested under “Menu” > “Applications”. I’ve tried but am unable to get SWFs to rest on my phone’s main menu beside “Applications”. It’s possible that I’m syncing incorrectly – it did take me a little while to realize that on S60 phones putting SWFs in the “Others” folder when syncing places them in the Flash menu – but doubt that’s the case. The Windows Mobile 5.0 devices come in last from a money-making perspective because there’s no system in place to distribute content to them and no prebuilt installers that I’ve seen.

Hold on. That last line is a little odd. How can it be that, “there’s no system in place to distribute the content”? Why do we need a network like Handango when we have the SMS/MMS network and the internet? Personally, I hope to distribute all of my Flash Lite content in one of the following ways: server SMS/MMS to device, email program SMS/MMS to device, and Bluetooth from device to device. The Verizon network is ridiculously locked down with proprietary installers, though, so we do need to use their network to get content on their BREW devices.

OK, back to recommendations. Unless there’s a way to make Flash Lite a first-class citizen on Symbian S40 phones, I feel strange even recommending them. I was pretty disappointed when my phone arrived and I couldn’t get a content icon on the main menu.

In conclusion, if you’re interested in buying a phone to experiment on with Flash Lite, I recommend getting a Symbian S60 2nd Edition or a Symbian S60 3nd Edition. I’ve bought my last three phones from Mobilebee.com, so if you can’t find a used S60 2nd or 3rd Edition somewhere (you should be able to find a used Nokia 6600) you might want to try them.

Have fun!

Tags , ,  | 6 comments

Comments

  1. erixtekila replied: Avatar Hi Luke, I wonder what you are thinking about deploying content to N60 mobile. I sometimes feels that it's really weird comparing to other technologies like java for ex.
    1. - Why the splashscreen Flash has to appear each time you want to launch an app. It makes to product not reallly branded IMHO.
    2. - The way to browse through your swf content in the "Other" folder is quiet sad also. No icon. This other folder seems to keep Flashlite in a bad sandbox, not accustomized for sellin content.
    3. - The article you mention with Carbide.c++ is for N60 3rd edition only and it only enable non commercial products to be done with. What a mess !
    4. - The lock down of content providers is just an awful market to enter in. Why can't we create our own ? What do you think ? http://reallyfreeflashgames.com:P
    5. - There is a really bad issue for the people who'd like to upgrade their flashlite version. It make the swf format not to be recognize after going to flahlite 2 version ! That's the most awful point I see in deploying content on Flashlite. Check this thread that talk of the issue : http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=68&catid=472&threadid=1220404&enterthread=y I wonder what the other think on all that in regards of selling content to mobile built with flash.
    Posted: about 3 hours later.
  2. Alessandro commented: Avatar Ciao great post! Just couple of things. Remember that your target devices are the ones that have Flash Lite embedded and not the ones where you install it. Which means no S60 2nd Ed should be a target device. S40 are Java phones, so you need to create a Jar/Jad type of installer. The Flash Lite implementation is geared towards wallpapers/screensavers. About the FL2.1 player splash screen, I would not worry about since the manufacturers will remove it. Just look at the Verizon implementation. There is no such thing of upgrading Flash Lite other then the possibility of the Operator doing it. Manufacturer will not provide upgrades, you just upgrade you phone, normal business! You can still sell self-signed (using Carbide C++ for packaing) but only unlocked phone will be able to install the sis, since operators usually disable the installation feature. Alessnadro www.biskero.org
    Posted: about 6 hours later.
  3. alimills replied: Avatar Great point Alessandro; target devices should be limited to phones that already have Flash Lite embedded. Since I've been waiting for Macromedia Adobe to deliver on the promise of Flash Lite for so long, I've almost lost hope that there will ever be target devices in circulation for me to develop for and share my developments with on my own. I thought I had figured out the process with my Flash Lite 1.1 Mobile Google Calendar, but just when Symbian S60 2nd Edition phones started shipping in the US (I bought a Nokia N70 with Flash Lite pre-installed), Flash Lite 2 was announced. Everyday it becomes clearer to me that the Flash Lite business model is about selling high-priced servers to service carriers and player licenses to OEMs. Sometimes, I think it shouldn't even be called Flash. Which leads me to...

    erixtekila,

    I agree with you on every point. So far, I've refused to install the FL2.1 player on my three phones because of the splash screen and am running FL2.0 instead (although that may change if input text in FL2.1 doesn't leave the app). I build installers with icons for all my apps using SWF2SIS because it results in a more professional end product that's a first-class citizen on my phone. Btw, what is the N60 mobile?

    Thanks for commenting guys, and thanks Alessandro for the pointer to create a Jar/Jad type of installer and the 3GSM photo. I'll look into the installer.

    Ali
    Posted: about 19 hours later.
  4. erixtekila commented: Avatar Allis, FlashLite 2 don't get that splashscreen ? Ouch, why did they add that ! On a side note, I should say that the mobile market is different in US than Europe (where I belong). Verizon ? BREW ?… Come on. There won't get any customer in that place for Flashlite for sure ! Sorry to complain.
    Posted: 1 day later.
  5. alimills replied: Avatar Nope, no splash screen with Flash Lite 2.0 or earlier.

    I also want to add that I do like Flash Lite and plan to start a third project this weekend. I don't fault Macromedia or Adobe for the issues surrounding it. I blame the cell phone industry...
    Posted: 1 day later.
  6. chall3ng3r commented: Avatar hi, just wanted to add that we have now made a solution for the Flash Lite content distribution problem, especially for games and apps. SWF2Go Professional allows you to make SIS distribution packages for all editions of S60 platform (1st, 2nd & 3rd). also, it makes menu icon, and supports all versions of Flash Lite, 1.1, 2.0 & 2.1 find more on www.orison.biz/products/swf2go/ you can sell your games and apps through handango.com // chall3ng3r //
    Posted: 46 days later.

Your Reply

Comment Form.

Fields denoted with an "*" are required.