8 ms·
Motorola Edge 20: gets the device resolution right (1018x2400) but somehow belives the screen resolution is only 432x960. I guess its using an incorrect dpi met
by andyjohnson0 3y ago
Motorola Edge 20: gets the device resolution right (1018x2400) but somehow belives the screen resolution is only 432x960. I guess its using an incorrect dpi metric or something, but its not clear how or why.
- tiffanyh 3y agoYou might be confusing PPI vs DPI. All smartphones these days have different PPI than DPI. https://graphicdesign.stackexchange.com/questions/6080/what-is-the-difference-between-dpi-dots-per-inch-and-ppi-pixels-per-inch https://graphicdesign.stackexchange.com/questions/6080/what-...
- chrismorgan 3y agoPlease don’t use the terms PPI and DPI and try to distinguish between them: it’s subtle at best and highly contested; in general computing, there is no difference, the two terms are used completely interchangeably. Only in a few niches is any distinction meaningfully drawn. (And the question you’re citing was largely talking about a different field, and half of its answers are mostly nonsense too.) The distinction you have is between what I’ll start by calling logical pixels and physical pixels. “Screen resolution” here is logical pixels, and “device resolution” physical pixels. Web specs call these CSS pixels (px) and device pixels (calculable in JS by dividing a px quantity by `devicePixelRatio`—which is incidentally subject to change within a page’s lifecycle, due to things like zooming in or out or moving to a different monitor), using a baseline of (simplifying quite a bit, actually) 96 dpi. Android calls the logical pixels density-independent pixels (dp), using a baseline of 160 dpi. (I think they’re the outlier in the size of their dp unit? Not sure how Apple works.) Microsoft calls the logical pixels device-independent pixels, using a baseline of 96 dpi.