Comment by qqxufo
10 hours ago
8K doesn’t create new design problems; it removes the blur that used to hide them. A quick checklist that keeps UIs sane across DPI:
Design at 1× first and preview at 100% OS scaling on a non-retina display.
Prefer SVG/CSS for icons/illustrations; avoid shipping @2× PNG backgrounds.
Use the system font stack; if you need web fonts, cap to two weights, subset with unicode-range, and font-display: swap.
Keep layer/effect counts low to avoid GPU over-compositing; rasterize heavy shadows.
Make images responsive (srcset/sizes) and lock aspect ratios to prevent reflow.
Budget third-party JS; measure on WebPageTest/Lighthouse, not just a dev box.
Do these and 8K stops being scary; most “looks bad on non-retina” is self-inflicted.
> preview at 100% OS scaling on a non-retina display.
Yeah, I feel like anyone who is serious enough to purchase a display like this ought to have a secondary display connected just for previewing their work on a "cheap" consumer device. It should be always available so that it only takes a few seconds to preview changes in the "worst-case" scenario by dragging a window over. It's why (good) phone devs test their apps on multi-year old devices.
This is why people working in pro-audio test mixes in lots of environments. Sure, it sounds great in a treated studio. How does it sound in the car? How about on headphones? What about on the built-in speaker on your phone? You want to hear the mix in the widest and most compromising scenarios to truly understand how well it holds up. Very few people have top-of-the-line hardware and most of your audience presumably don't.