Recently there have been some really good comments on my Responsive Mobile UI Split-Test: Icons or Text? post. Over the weekend a commenter named Yorke said:
Also might be worthwhile doing a quick broad device test to see how it renders across the ever changing continuum of device specs. On a quick test on a windows phone it doesn’t render well.
We have not been testing on Windows phone to be honest. It represents 0.25% of our visitors in 2014. We monitor our user base and try to test only on the devices/browsers that a substantial portion of our users use.
(I wrote specifically about which devices we test on and why in my post Browser & Usability Testing…Without Going Insane.)
If the goal was to build a perfect website that functions beautifully on all devices, then yes, we would absolutely have a Windows Phone and test on it.
However, that’s not the goal. The goal is to build a great business. It would be silly, maybe even insane, to spend time testing and refining on a device that represents 0.25% of our market when there are countless other things we could be doing to improve user experience for the majority of our customers, drive more traffic, increase conversion rates, increase efficiencies, and/or increase profitability.
It’s nothing personal. I actually think Windows Phones are pretty cool and innovative. I also think Ubuntu is cool, but I stopped testing on it when I realized none of our customers use it. Curiosity did get the best of me and I spent a few minutes using the Windows Phone emulation in Internet Explorer, and everything looked/functioned fine. That’s as far as I’m willing to go for now.
If our Windows Phone user base grows over time, then we will start testing on actual devices, although I wouldn’t bet on it, especially now that Nokia is releasing Android phones.
- Browser & Usability Testing…Without Going Insane
- The Data That Drove Our Responsive Design
- Why We Removed Our Newsletter Open-Tracking Pixel
- We Recently Migrated Detailed Image to Braintree Payments: The Good & Bad From This Large, Unplanned Project
- Regaining Control of Technology-Related “Emergencies”