> You start to think about what you design and build in a different way. You start to remember that the people using your web site aren't on the latest whiz-ba

> You start to think about what you design and build in a different way. You start to remember that the people using your web site aren't on the latest whiz-bank iPhone 16. They're on a craptastic pre-paid piece of garbage that they bought at 7-Eleven and share with other members of their family. Your realization is spot-on, but what's disturbing is that this is done by having developers work front desk-ish and hoping they learn the lessons, instead of being imposed, top-down, from a higher level. "We should write software for the kind of devices our users are using" isn't a story from the trenches, it's product and software development management 101. "We should target devices with these baseline specs" isn't something you get by having developers eyeball what phones their users are on, you get them by having Marketing put those fancy analytics tools that cost an arm and a leg every month to good use, and then by having those smart-ass program managers come up with a product definition that includes them, instead of the same generic "engaging, easy-to-use software that enables our customers to yadda yadda yadda" that gets cranked out each year. This way everyone's writing against the same specs. Otherwise the two developers who ended up in the VIP clinic and have seen nothing but iPhones all day will keep cranking out the code that turns the phones everyone uses into egg frying machines, while the other guys will write lean, mean software that the UX lead and the CTO will laugh at and then they'll go berserk about how premature optimization is the root of all evil because they're on iPhones, too, and the whole thing work just fine.