title: Android Hardware Acceleration - to use or not to use?
body: <p>I'm developing an app that it functionality very similar to Facebook Android native app:  social network that most of the time the user will spend in an endless <code>ListView</code> displaying lot's of images, entering an image gallery, and so on.</p>
  
  <p>let's say for the discussion that I'm doing all the right things and best android practices to  achieve smooth scroll (recycling views as it should, using different view types when needed, loading to memory only scaled bitmaps in the needed size, caching bitmaps, using ViewHolder design pattern, not blocking th UI thread when its possible and so on...) </p>
  
  <p>let's say also that every thing else in my app written in the best way and following best practices (for the discussion... :->)</p>
  
  <p>my app working not bad at all in that stage, but when
  turning on the hardware acceleration, as described and promised in <a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">Android Developers documentation</a> <strong>it making my app much much more smooth and fast.</strong>  </p>
  
  <p>let's say that it does not affect in any nagative way on the UI as can happened, and I'm not performing any of the <a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html#unsupported">Unsupported Operations</a></p>
  
  <p>according to Google's document on the subject, only reason I can see not to use this feature (besides all other reasons I already mentioned above) is that it can cause my app to use more RAM.   but how much RAM?   a lot more?  I know that when my app consumes lot's of RAM - it becoming good candidate to be destroyed by the OS when it need to free some memory.</p>
  
  <p>my question is basically - </p>
  
  <ul>
  <li>is it "ok" under my circumstances to use this feature?</li>
  <li>what other problems can raise from using it?</li>
  </ul>
  
  <p>TIA </p>