Antony has a new post mentioning good points about being careful on using device resources when developing mobile applications.

Recently I had a strange problem with my Nokia E61 device. The device needs to be charged every day. I was quite sure that the battery was still okay. The device was relatively new, about 1 month old. Before it happened, I could use my device for 3 – 4 days without charging.

Some of the main points he mentioned also apply Flash Lite and KuneriLite development:

Continuous timers, ticking too frequently (for example, more than once every five seconds), can adversely affect power consumption.

Soon, when we release KuneriLite, you will figure out the great benefits and use areas of our Timer plug-in. When we designed Timer plug-in, we limited the sequential timer sets to minimum 5 seconds in core module. Good to see we had a point there 🙂

If an application is moved to the background, it should, where appropriate, be paused and timers should be stopped.

This is already fine for Flash Lite development, due Flash Lite player pauses when it’s sent to background. In KuneriLite, there is always a server running in background, which has to be terminated by Flash Lite. We have to mention these points for developers to think very well when designing their architecture.

The backlight shall not be kept on without a good reason. It is turned off after a short period of inactivity is to conserve power; therefore overriding the system defaults should only be done if there is a compelling reason.

Flash Lite already takes care of that problem automatically (on S60 at least).

Communication technologies, such as Bluetooth and WiFi, should be used carefully, as there is always some drain on the battery when any network interface is active.

This point is also worth to be careful about. Developers using KuneriLite should be aware of that and design their application architecture properly. However, I don’t think that there will be too much problem there, due I don’t see any point keeping Bluetooth on for long time.

The camera has to be powered off when it is no longer used. Even if the camera is not being actively used, it is still consuming power if it is not powered off.

That’s also a point that KuneriLite users can feel safe about.