Hi,
I don't really care for platform specific icons, though I do care that
that we are able to provide don't fall into the same trap that Apple
have fallen into wrt display sizes and densities.
The microparsing of filenames (e.g. icon.png, [email protected],
[email protected]) isn't just annoying to implement - it's not really
scalable with the number of display densities and sizes we're likely to
have to support.
I do like Android's device independent pixels (dips), which allows the
dev to put resources in the display density buckets.
The bucketing that Android uses: ldpi, mdpi, hdpi, xhdpi, xxhdpi etc
seems to be a little more granular, but as Google are finding, it's not
granular enough, and they also want to differentiate between different
physical sizes of device.
https://developer.android.com/guide/practices/screens_support.html
The designers I've worked with who're used to the 1x == iPhone, 2x ==
iPhone Retina have discovered and re-discovered the information
contained in this blog post, which also be relevant here:
http://www.teehanlax.com/blog/density-converter/
Many thanks, and regards,
James
On 5/15/13 3:44 PM, [email protected] wrote:
Icon sizes and display densities
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
