dp animation maker exporting poor quality

The second lesson is that we should all be designing at 1x scale. For Apple devices it’s more like two or three different graphics.

This means that an icon that appears to be the same size on all of these screens actually requires 6 different graphics. Android is a perfect example: at the time of this article there are six common pixel densities across all the different device makers. But now it’s absolutely nuts - there are many pixel densities to support. In the early days of high resolution mobile devices, pixel density was as simple as 1x or 2x. On Android, DIPs are always based off 160 ppi. On iOS, a point varies from 132 points per inch to 163 points per inch. In other words there’s no single pixel density that represents 1 point - it’s dependent on the specific device (see Perception of Scale section below). But if you’re really curious, know that on Apple devices there’s no constant conversion between inches and points.

Designers just need to trust that the device maker has settled on a pixel density that is appropriate for that device, and focus our attention on preparing design assets at 1x, 2x, 3x, or any other ratio. There’s actually very little practical need for UI designers to worry about it, because we have minimal control over device-specific alterations. You may be wondering about the physical size of a point. They’re a universal unit of measurement, that can be converted to pixels using a device’s scaling ratio (2x, 3x, etc.). They’re not exactly equivalent to points in iOS, but the idea behind them is the same. They aren’t called “points”, they’re called “DIPs”, which stands for density-independent pixels. Google has defined their own density-independent unit for Android. But this isn’t just for Apple devices of course, these days every operating system - desktop or mobile - supports high ppi/dpi screens.

Dp animation maker exporting poor quality