Optimizing Android application before release
I'm in a "*special*" (or *normal*) situation about **effeciency** of my program. Now I'm at a phase where I want to maximize my application; be *top notch* and reduce the *battery consumption*.

Before going to the question:

 - **First**, my application work. It runs fine - no errors *whatsoever*.
 - **Second**, I have read [Designing for Performance on Android developers website][1] and I have optimized small things they're mentioning. No problems *whatsoever*.

Now, I'm curious to hear about developers "*special*" tricks (fixes) that optimized their application(s). Stuff that users never gonna recognize or pay attention to; but instead increased the battery life or effectively made your application easier to maintain.

So, **what's your unique optimizing trick(s)?** (e.g. Object Pools? why? other patterns? unknown things? things that the website forgot to mention?) It doesn't have to be Android specific.

I hope this question isn't vague or subjective (if you think it is I'm apologizing for that). **But**, I'm in a particular situation where I'm really looking for knowledge and I think this will be a great opportunity to share developers knowledge, about a situation they have all been in.

Please, vote up great answers as that will encourage great developers to share their knowledge.
Optimizing Android application before release
===

I'm in a "*special*" (or *normal*) situation about **effeciency** of my program. Now I'm at a phase where I want to maximize my application; be *top notch* and reduce the *battery consumption*.

Before going to the question:

 - **First**, my application work. It runs fine - no errors *whatsoever*.
 - **Second**, I have read [Designing for Performance on Android developers website][1] and I have optimized small things they're mentioning. No problems *whatsoever*.

Now, I'm curious to hear about developers "*special*" tricks (fixes) that optimized their application(s). Stuff that users never gonna recognize or pay attention to; but instead increased the battery life or effectively made your application easier to maintain.

So, **what's your unique optimizing trick(s)?** (e.g. Object Pools? why? other patterns? unknown things? things that the website forgot to mention?) It doesn't have to be Android specific.

I hope this question isn't vague or subjective (if you think it is I'm apologizing for that). **But**, I'm in a particular situation where I'm really looking for knowledge and I think this will be a great opportunity to share developers knowledge, about a situation they have all been in.

Please, vote up great answers as that will encourage great developers to share their knowledge.