Printable View
Gotta create an Android app logo, but the new requierements are super vague for me, anyone done this before?
https://developer.android.com/guide/..._adaptive.html
https://material.io/guidelines/layou...urements.html#
Would much appreciate a bit of explanation here, thanks.
It looks like it's fancy BS techno-jibberish-nothing-burger-sales-tactics-feature-bloat-with-no-historical-context. Density independent pixels is literally referring to vectors. YOu draw a shape, give it a percentage of screen realestate to take up and the renderer will figure out how many pixels wide/tall to display it for you.Quote:
Originally Posted by Mcffee
It's really just a bogus terminology that completely ignores existing technology and terminology. I wouldn't sweat over it too much. If you design SVG icons for a system that can load SVG, it's the same thing, as long as think in terms of percentages. You can make special cases for common resolutions if you need things specifically spaced a specific number of pixels for your specific look, but getting into that level of detail is a largely both unnoticed and unappreciated from an end user's perspective.
TL;DR answer: Stick with percentages if you know your software/webpage is not always going to be viewed on a specific kind of display and use vector/shapes as much as possible to avoid ugly edges and rendering. It's been an acceptable standard and supported by W3 since forever and a half ago. Google is trying to confuse you.