Hartti Posted 20 tips for Flash Lite development by Alessandro Pace and Dale Rankine which due limitations of time ended up being more like 17 tips for FL development. So I think we have to wait for the remaining 3 tips until the presentation slides are online 🙂

Following are the tips  in the order of the presentation as collected by hartti :

1) Use templates in authoring, they set the stage, frame rate, player version, screen size, etc…. you can also create your own templates

2) Optimizing animation: remove unnecessary points from vectores, fills instead of strokes, ActionScript over tweening, avoid heavy use of alphas (or anything requiring heavy calculations), and TEST ON THE REAL HANDSETS

3) Create efficient code by accessing on each device only the available features (what about the increased size of the application???)

4) Portable content: use average screen size as stage, allow the content bleed off the stage, some devices will scale differently -> test

5) Catching keys: FL 1.1 – a button as listener (works also on FL 2), FL 2 – an object as key listener

6) Follow the UI conventions of the handset, make sure text is easy to read, read Josh Ulm’s paper “Designing Engaging Mobile Experiences”

7) Tracking static and dynamic heap: Can be done in CS3, but still experiences on real devices may differ (e.g. running multiple apps simultaneous on the device)

8) You can start new documents from Device Central!

9) You can embed Flash Lite content on a mobile site (need to detect devices supporting FL in browser, like S60 3rd Ed WAP browser or S60 3rd Ed FP1 browser)

10) You can test different times and dates with Device Central

11) Use RDA (Forum Nokia Remote Device Access) for memory issues, fscommand2

12) Use Device Central to test device performance, you need to recalibrate as the performance of your desktop can vary

13) DRM, FL contents is treated like an image (passive content), you can use Nokia Mobile Internet Toolkit 4.1 to wrap swf file with DRM (BTW Alessandro, I am pretty sure the forward-locked content is encrypted on the terminal using a terminal specific key, so you cannot just copy that file with USB cable…)

14) Use device sets in Device Central, exporting/importing device sets within a dev group

15) Memory management – read the article in Adobe dev central

… (running out of time..)

17) Design content using multiple SWF, a shell swf which loads modules

18) Re-use assets, increase productivity/profitability

Great tips 🙂 Thanks Hartti to making this live.

vivek