Huh. I checked the source code on this one and all it’s doing in wrapping an iframe inside a picture of the mobile device. While this can be useful, it really does nothing more than you can do by making your browser window narrower as it’s using your browser’s rendering engine instead of the renderer of the actual device.
For testing iOS devices, I use the iOS simulator that comes bundled with Xcode. This tool works well and employs the actual Safari for iOS engine.
In my search I have also found that Google themselves offer a free browser extension named “Responsive Web Design Tester” that appears to cover cross platform devices that can be manually updated and adjusted - just wanted to share this with you all
Unfortunately, that tool uses Chrome’s rendering engine instead of each devices rendering engine:
RWD tester also uses the correct User-Agent, but it does not render web pages in the same way as the mobile device.
Basically, it does the same thing as shrinking your browser does.
Let me briefly give an example of why these “responsive testing” tools don’t suffice. We’ll look at iframes. Simple, eh? Set the iframe to have a width of 100%, and in Safari, Chrome, Firefox, Opera, and even IE, the iframe will flex and shrink as the viewport changes size. You even use some of these “responsive testing” tools to cover your bases. You think everything is fine and dandy, until you look at your awesome responsive website with your iPhone. Suddenly, the iframe is huge, overflowing it’s container and wreaking havoc on the layout! What’s going on here? Well, for some reason the chaps in Cupertino decided that in Mobile Safari they wouldn’t let an iframe be smaller than the website it contains. If the website inside the iframe is 960px wide, the iframe will be 960px wide, much wider than the width of your iPhone screen.
You would never know of this problem unless you checked it with your iPhone (or the iOS simulator). It worked great in all of your desktop browsers, and in the in-browser responsive testing tools! So, you search Freewaytalk, find a fix, and go happily on your way; the world is at peace once again.
There currently are only two ways to really test your website:
Run the OS. This means either through a VM, or an actual device.
Any other method/tool I’ve ever seen simply uses your browser’s rendering engine and does no properly emulate what a mobile device user will see.
When It comes to testing… Use the best and most reliable tools. In the end you will save time, which is money and you will deliver a better product.
Unless someone has found discrepancy’s with the testing tools at BrowserStack, and please advise if you have, I strongly recommend them.
Testing, retesting and then even more testing and even still the web as a medium may throw you a curve ball. It is just the way of things, so there is no substitute for reliable tools and services, that help you in this endeavor.