The way people consume information is constantly evolving. As web designers and developers, we keep up with all of the different screen shapes and sizes, learning to create beautiful, flexible software. Yet most of the available tools still don’t reflect the nature and diversity of the platform we’re building for: the browser.
When I was making my first responsive website in 2012, I quickly realized how inefficient and time-consuming the constant browser window resizing was. I had just moved from Estonia to Australia, and with a newborn, time was very much a precious resource.
I began looking for better ways to see the effects of my media queries.
I came across Matt Kersley’s Responsive Web Design Testing Tool1 and was blown away. It cut my development time in half. Even though the app was quite basic, it quickly became indispensable, and I continued to use it for several years.
It was very much to my surprise that I never saw this brilliant concept taken any further. This, combined with the lack of features, set me on a journey to create the open-source virtual device lab XRespond74.
Understanding The Problem Link
When it comes to developing responsive websites, the problem lies in having to constantly resize the browser window. Although this unavoidable action feels second nature to most, it also masks aspects of design we don’t often appreciate — most notably, inconsistency and time management.
With designs usually appearing in some combination of mobile, tablet and desktop context, anything in between is left in a somewhat uncertain state. And filling these gaps requires a lot of time and effort.
The problem lies in the difficulty of looking at one screen size at a time, as opposed to getting an all-in-one overview of different screen sizes. When we’re building for a variety of screen types, it doesn’t make sense to view only a single instance of a design at any given time — we’d be unable to gain the context of how the styles of elements change across breakpoints.
Current practices just don’t cater to these modern ways of developing. Fortunately, it’s not all bad news.
Simple Solution Link
XRespond74 is a virtual device lab for designing, developing and testing responsive websites. The idea is simple: It enables you to make website comparisons side by side, as if you had different devices on the wall in front of you.
You don’t have to leave your desk, laptop or even favorite browser. And with zero setup, you can start comparing websites right away.
XRespond can help if you’re building a pattern library or a style guide, because you can focus on a single component at different screen sizes simultaneously. As you’d expect from a development tool, it works well with local servers.
Just bear in mind that, as with any emulation, XRespond can’t compete with testing on real devices, but it will get you 90% of the way there — and in a fraction of the time.
How To Use It? Link
Enter a website address, click the button, and XRespond will automatically display the website on different virtual devices — which you can choose and customize as you see fit.
XRespond works well with other development tools, notably one of my favorites: Browsersync10. Browsersync enables you to set up live reloads and synchronized scrolling — all simultaneously across virtual (and real) devices. This makes spotting problems simpler, because issues become more apparent.
What To Do If Your Website Won’t Load? Link
Occasionally, you might run into a problem of your website failing to load. This most likely has to do with your website preventing itself from being loaded in an iframe. If you own the website, you can temporarily disable
X-Frame-Options13 or the Content Security Policy14, depending on your setup.
I love XRespond — and not just because I love making it, but because it simplifies my life. I can spend less time and effort working, and use the spare time for something else. It’s given me an opportunity to improve the quality of my work. I hope you’ll find XRespond just as useful and will start enjoying the time it saves you.
(da, il, al)
- 1 http://mattkersley.com/responsive/
- 2 https://www.smashingmagazine.com/wp-content/uploads/2017/08/mattkersley-large-opt.png
- 3 https://www.smashingmagazine.com/wp-content/uploads/2017/08/mattkersley-large-opt.png
- 4 https://www.xrespond.com
- 5 https://www.smashingmagazine.com/wp-content/uploads/2017/08/xrespond-large-opt.png
- 6 https://www.smashingmagazine.com/wp-content/uploads/2017/08/xrespond-large-opt.png
- 7 https://www.xrespond.com
- 8 https://www.smashingmagazine.com/wp-content/uploads/2017/08/xrespond-banner-large-opt.png
- 9 https://www.smashingmagazine.com/wp-content/uploads/2017/08/xrespond-banner-large-opt.png
- 10 https://www.browsersync.io/
- 11 https://www.smashingmagazine.com/wp-content/uploads/2017/08/browsersync.gif
- 12 https://www.smashingmagazine.com/wp-content/uploads/2017/08/browsersync.gif
- 13 https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
- 14 https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
- 15 https://twitter.com/indrekpaas