This week we talked about how you can easily detect the battery status, and respond to that status. It's become more and more critical that the experiences you create for the end user respect battery status, and if you conditionally operate in a way that preserves that status, your user will be more happy.
It's extremely easy to do this, as we demonstrate in this short video... of course just part of the puzzle in terms of what you may choose to do to create a great experience for your user. You yourself will have to determine exactly how to conditionally change the behavior of your app in order to deliver the better experience, and to some extent this will require that you deduce what operations are more power hungry than other. Some of these are relatively obvious, others less so. Perhaps the best approach is to test your application in the real world on a real device and see what the experience is like; another option would be to use these APIs to create an instrumented version of your app so that you can test and determine power consumption impact.
Here are more resources for you on this topic: