FlashLite3.0 최적화 관련 Tip

Posted 2009.06.01 11:02
  1. Trace reports when publishing from Flash
  2. Optimize your assets, till you have sqeezed out every byte.
  3. Limit the amount of keyframes you use in the timeline
  4. Use TweenLite from Greensock for tweening assets
  5. Avoid at all times using timers or onenterrames
  6. Avoid using new variables inside a loop

  7. Check out JFSL  (Javascript-xFlash)
  8. Preprocess AS2 when you’re done http://www.asual.com/enlarge/
  9. Use feedback on buttons, audio and animation because there’s no rollovers in the mobile world
  10. Know your device…Sony Ericon keeps its own titlebar + toolbar, Nokia can go fullscreen…
  11. Don’t use alpha=0 or visible= false but use a blank keyframe! It stays in your memory and doesn’t get garbage collected otherwise

  12. When loading in external movies or assets when you unload them they will stay in the memory even when destroying everything…so just load in another asset within the same object to destroy it.

  13. Use the Nokia PC Test Suite software
  14. Use http://www.deviceanywhere.com/ to test your application on any network in the world.
  15. Data structure: Loading data cost money, load only data that is needed/displayed Always ON DEMAND
  16. Try to avoid large XML data(chunk it !!)XML versus &name=value pair ?

  17. Make sure you have control over the data. Messaging scheme: info/warning/error
  18. Media content mobile friendly (image/audio/video): use specific formats/bit rate,
  19. Use 3gp for video and .aac for audio. Flash Lite 3.x use .flv
  20. Use large devices sets to test on.
  21. Mobile users are used to certain UI layout and navigation. Refer to mobile UI guidelines from OEM
  22. Make sure navigation is clear & simple
  23. You MUST have an EXIT button

  24. Stay below 70% “Memory”, No Classes! -What? (Classes, consume memory)
  25. Memory allocated by OEM to the Flash Liteplayer check Device Central
  26. Memory fragmentation is a problem
  27. Garbage Collector (GC) uses memory (Runs every 60 seconds and for > 20% memory increase)

  28. 32 Kbytes rule
  29. Do not compress SWF
  30. Do not embed fonts
  31. “delete” global objects

  32. “null” variables, local objects
  33. Memory is freed when Object reference count = zero , otherwise Memory Leaks!
  34. Use multiple SWF architecture, unload movie clips to free memory
  35. Crash test in real scenarios: Home/bar/restaurant On the bus/metro/train.
  36. use http://demofone.com/ for presenting your mobile application

Write your message and submit
« PREV : 1 : 2 : 3 : 4 : 5 : 6 : 7 : 8 : 9 : ··· : 18 : NEXT »