Welcome to 3V and thank you for stopping by. We hope that you will take the time to read this article and learn a little about the history of responsive web design (RWD) and takeaway from this article valuable information about one of the tools that we routinely use for mobile website and web app testing, the Chrome Mobile Browser Emulator.
Every professional web developer, designer and even most DIY designers are challenged with the unenviable task of designing, publishing and testing their website on multiple devices and multiple browsers. I remember in the formative years of web 2.0, IT and technical professional referred to this challenge as “device agnosticity“, which incidentally I find to be a near malapropism, a bizarre combination of words;
During the 2000’s, I was simply programmer (a foot soldier if you will) so I thought it was cool to be involved in “device agnostic” design meetings, building web applications based upon the needs and requirements of business analysts, managers and executives. Nonetheless, the challenge in the early to mid 2000’s was the publishing of web content that would render consistently on multiple browsers and multiple OS’s. Fast forward a couple of years and with the incredible growth of smart phone and tablet consumers, IT and technical professionals were challenged with not only browser compatibility and OS compatibility, we now have to deal with device compatibility.
As web 2.0 evolved, as browser standards continue to develop and as technology professionals push the envelope of UI/UX design, responsive web design (RWD) started to become mainstream. During the formative years of RWD, 2008-2011, designers used terminology like “flexible”, “liquid”, “fluid”, and “elastic” design. The adolescent years of RWD, 2010-2012, was crucial point and fork in the road that the web design community began to embrace and build upon responsive user interfaces.
I recall conversations dating back from 2012 to 2014 where clients, partners and other agencies emphasized to us, 3V, the importance of designing and publishing responsive web sites. In 2015, we are WELL beyond that conversation (much like in 2010 if you asked someone if they owned a cell phone, you would not dare ask that question for it is a simple assumption that everybody has one). No longer must a client request a mobile friendly website, now it is a foregone conclusion that web designers and developers build to a standard of responsive web design.
Designers and developers utilize a host of tools to test device, OS and browser compatibility. Testing web assets on each device, OS and browser is VERY time consuming, tedious and downright boring! That said, we have come across a tool that we simply cannot live without, the Chrome Mobile Browser Emulator.
There are a thousands of emulators out there but let’s face it, if you are not a PhD of software engineering finding a user friendly solution can be a challenge. The tedious and time consuming method for testing devices and browsers is to pull out your phone and/or your tablet and open a URL or web app. The less than optimal method of testing device sizes is to resize your browser window and test the “fluidity” of the website or URL. Each of these methods serve an important purpose, but when it comes to true quality control The Chrome Browser Emulator will provide you with these benefits;
If you are looking for a more consistent, quality and time saving means of validating, testing or verifying your website is truly responsive and renders perfectly on all types of OS’s, browsers and devices, follow these steps to install and use the the Chrome Mobile Browser Emulator.