Why Pixel Perfect Design sucks
You want your webseite to look the same. On all devices. Perfectly the same.
That makes sense.
I've seen this approach many times in organizations where product owners are not really connected to tech. And where responsible managers did not really understand the implications of pixel perfect design.
The truth is that Pixel Perfect Design costs real money.- Testing on many devices costs money.
- Developing for many devices and making that pixel perfect costs money.
Of course money equates time.
And organizations that implement Pixel-Perfect-Design for many devices are slow. And that's the opposite of innovation. Ouch.
The reality - enter Pixel-Good-Design
Dirk, a colleague of mine, drafted a new term: Pixel-Good-Design.
We don't want crappy pages. But we also don't want to spend a lot of time and money on pixel perfectness that does not translate into business vale.
The middle ground is Pixel-Good-Design: Test on your most important browsers and you a ready to go. If you find imprefections on some nieche devices then either accept them or fix them.