On Tue, Jul 24, 2012 at 3:08 AM, Dianne Hackborn <hack...@android.com> wrote: > In this case providing the different densities > yourself is pretty much entirely a performance optimization -- the platform > doesn't need to do the scaling at runtime when loading your resources.
It's also a bit of a quality-control optimization. Different scaling algorithms give different results, and it stands to reason that Android's will be optimized more for space/time than would, say, all of Photoshop's. Plus, Android's scaling algorithms might change over time (or conceivably be modified by OEMs) -- scaling them yourself puts *you* in control over the final image look and feel. While that may be overkill for many apps, there will be some whose designers want that level of control. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.8 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
