Typical embedded system is limited in CPU and memory. Flash content often dictates the CPU and memory requirement, and could easily make or break the device. Therefore, Flash Lite content running on embedded system must be written so that you consume as little memory and CPU as possible. While doing so, the designer must also pay attention to the quality of work, and come up with the tradeoffs in performance vs the ‘looks’. Here are a few tips to optimize your content for images, and vector graphics.
1. Bitmaps consume more memory than vecor counterparts. However, the advantage of bitmaps is that it provides a much detailed image. The swf file can grow rather large in size with bitmap impages. Flash Lite can only load a swf file of the order of say 1-2 MB on a low end cellphone device. Keep that in mind while writing content.
2. If you are looking to scale or rotate a bitmap, it is very CPU and memory intensive. So if your application requires scaling or rotating, you are better off using vector graphics.
3. Consider lowering of resolution of the bitmap images. Several handsets have a lower resolution screen, and if you are targetting mobile devices, you may not need the highest resolution.
5. Flash Lite does not support bitmap smoothing. A bitmap image thats not ’smoothened’ will look ‘pixelated’ or ‘jagged’. For example, the text below is not ’smooth’.
but the text below appears ’smoothened’ at edges.
So if you are looking to create content that requires ’smoothing’ , Flash Lite is not the way to go.
Share the post
These icons link to social bookmarking sites where readers can share and discover new web pages.