Jun 28, 2010
What possible reason could there be for you to code your apps so that they switch on in the background when the phone is turned on and use up precious battery life?
View 13 Replies
Or, why would you code your apps to stay on after I, the user, have hit the back button because I no longer want your app to run?
I mean, REALLY! Yes, I own up to being a newbie Android user, and what I don't know could fill the Library of Congress. Still, this is common sense we're talking about here. I've done some industrial app development and Enter/Exit, On/Off are basic pieces of logic in the main loop of an program in any language.
The only reason that we phone users need task killer apps is because you developers insist on creating apps that don't know when the f**k to turn themselves off.
And, it seems to me like you, the app developers, are one of the main reason why these phones have such crappy battery life. I mean, my Samsung Instinct, as bad as it was, got 18 to 24 hours of life off of one charge. With the Hero, I'm lucky if I can get 10 hours, and that's even with configuring my email download to only three times per day!
This is not hard, people. You code the app to stay off until, I, the user, manually turn it on. AND, you also code it to turn off when I, the user, hit the back button.
Yes, I understand that there are certain apps that it is advantageous to keep running in the background. So, fine, make it so those keep running. BUT, there is no possible reason for apps like Flashlight, or BBC News, or Camera, or SprintTV to have to run all the time in the background!
I am so tempted to just trash the lot of you. If I did, maybe I might not have as much functionality, but my teenager would be able to reach me late in the day because my phone battery would still have juice.