The biggest obstacle (of mine) since I rolled out the Responsive DIY Template Default for v1.5.x is getting not only shop owners but contributors and developers to understand the difference.
Responsive Design is a (minimal) design and one should build their website (template) with that in mind.
If one chooses to use responsive code and media queries, they choose minimalism, 1 template file, 1 module file, 1 css file.
Counter productive to ME (IMO) is creating the same page 3 times to produce an outcome. When the only outcome that matters is that the (add to cart) button gets clicked.
If Bootstrap is your building ground (great), I started their as well. But Bootstrap is a CSS framework that offers (4), yes (4) media queries to build a responsive design, however Bootstrap hasn't even tapped into the media query expressions available.
Media Query Expressions that are very much similar to those used in the Google device detect code.
Are Media Queries enough? That is the question.
This is the answer.
If you want one website template, one file to edit, a minimal design focused on selling products and providing a consistent but minimal user experience. Then Yes, media queries are enough.
If you want multiple templates and files to manage, then No, media queries are not enough.
A good responsive design will scale down from desktop to tablet without major changes only hiding the (access) not so important information from phones.
This is a discussion that has been going back and forth with developers and designers for years.
I put my 2 cents in, I have heard all the "arguments", I weighed the pros and cons. I choose media queries over several different template designs.
If one doesn't understand media queries and media query expressions:
http://www.w3.org/TR/css3-mediaqueries/
If one is still ignorant to the tools available for testing media queries:
http://www.we-are-gurus.com/tools/re...ign-tester.php
http://responsivepx.com/
All popular browsers offer build-in user agent switchers, so you can change your user agent without installing any extensions. Google Chrome and Internet Explorer both include user agent switchers in their developer tools, while Firefox offers an about:config option.
Websites identify browsers by their user agents. Modify a browser’s user agent and it will appear as a different browser – or even a browser running on another device, such as a smartphone or tablet.
Bookmarks