Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Why provide multiple drawables for various densities?
Lets say I have a splash screen which is scaled in a way to always fit the full screen.
Does it make sense to package 4 different density version of the same image?
Why not let android handle the down-scaling?
Another example would be button icons. Why not packaging only xhdpi and let android do the work? Is it a memory issue?
That depends on whether you like the results of the downscaling. If you do, use it. If you don’t, supply other artwork for the densities that need it.
Partly, it is a speed issue, as downsampling takes CPU time (and, hence, a bit more battery).
Partly, it is a quality issue, as the downsampling that Android does means you are not in final control over what the image looks like. You might be happy with the downsampling of your images; other developers may not be happy with the downsampling of their images.
For example, the Nexus 7 is a
-tvdpidevice. However, Google doesn’t bother with-tvdpiimages — they let Android downsample the-xhdpiimages. The images seem perfectly reasonable to me, and apparently to Google as well. OTOH, Google does ship-mdpiimages, not only for-mdpidevices, but to serve as the basis for downsampling for-ldpi.