Workflow with Flash Lite and Device Central

When working with Flash Lite and Device Central, to simplify things a certain workflow method is recommended to be picked up. For example, begin in Device Central (decide your platform, etc) > Move over to Flash and start building it up > Package it to .SIS > then distribute.

Note: Packaging is a term used in mobile development to describe the process of gathering and compressing numerous files together in to a single file with a specific format that’s then interpreted by a device. Once placed within the device the package can then be launched or installed. Within the mobile platform category there are several types of packaging formats, such as:

Symbian – .SIS

Windows Mobile – .CAB

Java Applications – .JAR

Nokia Series 40 – .NFL

When creating Flash Lite content, the process will become very iterative as there will need to be constant switching back and forth between Flash and Device Central. Here’s a detailed overview of how I would recommend a simple and logical workflow.

Identify your target device and Flash Lite content type: Obviously different devices have different screen sizes, support specific types of video/audio formats and have different colour screen depths, among many other factors. These factors may well influence your applications design and implementation.

In addition to this, different devices support different Flash Lite content types (e.g. screen savers, video ring tones). The type of content which you are also developing for will also determine what type of features will be available to implement within your application.

Create the application in Flash and run a simulation in Device Central. Device Central CS3 includes an emulator which allows you to transfer your Flash application to it and emulate it as if it were on a phone, without having to actually transfer it to a phone. This allows you to quickly refine your application and correct and errors before transferring it to a mobile phone.

Test the application on your target device(s). This is an important step as you cannot solely rely on the Device Central. The Device Central won’t emulate every aspect of your device; this includes your processor speed and even the colour depth. For example, an animation that simulates smoothly on Device Central may not run as smooth on your mobile device due to its lower processing power, or a gradient that appears smooth on Device Central may appear banded on your device due to the colour bit depth. After testing the application on an actual device, you may find that some further refinements are required to the design.

The recommended work flow procedure