It can at times behave very differently from MacOS (desktop) Safari. So when it comes to testing and debugging iOS Safari, my options are limited.Ĭompounding the problem: iOS Safari is very much its own beast. I, personally, have never owned one, and nobody in my household currently uses one. In my case, an iPhone is the missing piece. It’s just a fundamental truth of web development-one which presents a challenge for those of us who don’t have easy access to all relevant devices. No matter how much you’ve stretched and compressed your browser window to mimic the proportions of a mobile device, you haven’t really tested your project until you’ve tested on the device itself. You lean forward, staring through narrowed eyes at some bizarre mutation of your carefully crafted code. Is it the cache? Did you type the URL wrong? No… Maybe you even feel some denial and hit the refresh button once or twice. And so you grab an iPhone and pull up the staging URL. Suddenly, it occurs to you: you haven’t tested it on iOS yet. You’ve poured your heart and soul into it, and you’re close to launching it for the world to see. If you’re like me, you’ve experienced this more than once: you have a pristine new web project you’re excited about.
