Pixels, points, and screen density.
Pixel judgment can feel different from one device to another. A shape that looks large on a phone may feel modest on a desktop monitor. To understand what Pixactly trains, it helps to separate physical pixels, CSS pixels, points, and screen density.
Physical pixels are hardware
Physical pixels are the tiny light-producing units on a display. A high-density screen packs more of them into the same physical space. That is why text and UI can look sharp on modern phones even when the interface is not physically huge.
CSS pixels are layout units
Web layouts usually deal with CSS pixels. A 100px-wide element in CSS is not always 100 physical device pixels. The browser maps CSS pixels to the screen in a way that keeps web interfaces usable across different densities and zoom levels. Pixactly's targets are about this rendered layout space: the size you see and interact with in the browser.
Points are common in design tools
Designers may also think in points, especially when moving between interface design tools and platform guidelines. Points and CSS pixels are not always identical concepts, but both are attempts to describe usable visual size rather than raw hardware dots. The practical design question is usually, "How big does this feel to the user?"
What Pixactly actually trains
Pixactly trains your eye for rendered dimensions in the current browser environment. If you practice on a laptop, you are calibrating against that screen, zoom level, and viewport. If you practice on a phone, the feel changes. That is not a flaw. It reflects real design work, where components must be judged in context.
The transferable skill is not memorizing one physical size. It is learning to compare dimensions, notice proportion, and adjust after feedback. Those skills remain useful whether the final interface is built in CSS, a native app, or a design tool.