and project requirements when making decisions on what devices to invest in. Asking questions is a great exercise. What's the nature of the project? Who's our audience? What kind of phones are they using and more importantly, how are they using them? What are the technical requirements of the project? It's also worth noting that looking at site analytics is a great exercise, but beware as they can often misrepresent many (largely non-iOS, non-Android) devices. So definitely use analytics to your advantage, but don't use them as an excuse to throw non-iOS, non-Android phones out the window. joey so basically, while even big companies stop to support IE6 because it costs too much ressources, you consider testing every crappy and old phone is an option ? "look at your user audience"... right. Then reduce your testing set (btw you didn't even mentionned Windows &lt; 7). my theory is that people owning a phone with a crappy browser give it a few tries, see that it's unusable and stop trying. you might have a 100% usable site on their phone, they won't even try to load it until they buy a new phone with a modern browser installed. they gave up already. Hi Joey, The theory that people don't use browsers on devices with crappy browsers is unfortunately false. The phrase "The best camera is the one that's with you" definitely applies to the mobile web. For example, I was talking to my geologist cousin while home for the holidays. He