If You're Programming a Cell Phone Like a Server, You're Doing it Wrong
> Every decision you make should be based on minimizing the number of times the radio powers up.This is lunacy. Ok, lunacy is a bit strong. But I disagree with this and am throwing a "premature optimization" flag.Modern phone batteries last plenty long, and the radio being on is nothing compared to the big bright screen./edit
Given the opportunity to chose, I know I would gladly sacrifice a few minutes per charge battery life for a better user experience, especially since my phone never gets below 20%.Your users will be better served by you fixing bugs or adding features. Really, unless you're a huge team with a huge budget, there's other stuff to worry about in your app experience before "maximizing battery life" should be a responsibility you want to help the OS/device maker with.(If you're one of the lucky ones who has the time and money to do both, by all means, go nuts.)Being conservative with resource usage is sound advice. Making battery usage the prime concern for most apps is overkill.Games and other applications that you know users will have open for extended periods of time, and/or that are already eating up battery should give this issue some thought, everyone else, really, don't worry about it.