Responsive Design Part 1: What is responsive website design?
4 Jan 2016
Everyone and their cat has a responsive website now don't they? They all think they're so cool with their responsive websites that do responsive things in responsive situations. You know… responding to things that require responsive responses...
The sad truth
The trouble is that while everyone is gassing about this 'responsive' buzzword, and throwing it around like they're namedropping, the truth is that a lot of the people who are talking about responsive (and even more tragically those who claim to offer responsive websites), don't actually know what responsive is.
So in this series I'd like to get stuck in to what responsive really means. What is a responsive website? Why should you have a responsive website? And perhaps more importantly… what isn't a responsive website? And also to have an honest discussion about some of the pitfalls of responsive design and how they can be avoided.
But for now let's get on topic (and hopefully stay there) by discussing... WHAT is responsive design?
More than just another TLA (three letter acronym)
Responsive website design (or RWD if you're someone who enjoys using acronyms to confuse people) is a craft much like plastering a wall or wiring a house. You have to combine theory and practice with common sense and of course individual artistic flair.
You'll often hear people say: “responsive design means it works on mobile”.
Just to be clear… all websites work on mobile. They might not work well, but they all work on mobile because the mobile browsers were designed to deal with websites as they were before mobile browsers even became a thing.
What we're really talking about is optimisation of visual style and content for any devices other than a standard desktop machine or laptop so if you hear someone talking relentlessly about mobile websites, you might need to run for the hills.
So what is responsive design then?
Responsive website design can be best summed up by looking at the user experience. Responsive website design will allow a user to achieve a goal on any device (this is important as too much focus is placed solely on mobile) without obstruction or annoyance. This means that responsive website design isn't just about “making it work on mobile”. It is about refining the experience of the desktop site so that it works better for a reduced screen size and touch screen input. This can mean that elements on the page should re-flow and resize to suit the 'viewport' (i.e. device screen size) and in some extreme cases change form, or even disappear altogether.
When Adobe introduced the concept of responsive to their print design software InDesign they referred to the method as 'liquid layout' and I love this terminology. Imagine your device browser is a cup and the website is water and the page components are the molecules. In the words of the late, great Bruce Lee: “You must be shapeless, formless, like water. When you pour water in a cup, it becomes the cup. When you pour water in a bottle, it becomes the bottle. When you pour water in a teapot, it becomes the teapot.”
How does it work? (Geek speak alert!)
I'll try to explain this as simply as I can! Responsive design works by reacting to both browser and device size. Using CSS code we write 'media queries' which means that unique styling code is written for different breakpoints or browser widths. Then before the browser renders a block of styling code to the screen, it crawls the various 'breakpoint blocks' of code and applies the correct one depending on the width of the browser at that time. A fully responsive website will change before your very eyes as you scale the browser width up and down on a desktop machine because the browser will continually update the rendered code as its width is changed. These are the 'breakpoints' telling the code dynamically which set of CSS code to pull out and use, depending on the device size and browser being used.
Proper responsive design requires human decisions
As great as technology is, we mere mortals are still required to make the decisions that shape the websites of tomorrow.
Everything must be considered.
If menu items tuck away off screen the trigger to access them needs to be easy to spot and easy to access. If items that aren't the main content are shifted for smaller screens there needs to be some logical and rational decisions as to why they will move and where they will move to. If you're going to remove certain items for a smaller devices this needs to be carefully considered and only implemented in instances where it aids the user experience, and doesn't upset the user goals of the site.
EVERYTHING must be considered!
Every single element on a website needs to be considered for all device sizes. It's not good enough to just take care of the larger components or main regions and leave it at that. It is also not enough to just make the main pages responsive and then leave everything else to break. This will create an horrendous user experience but we've seen this more times than we care to recall and it truly pains us to see. From the background to the images to the font sizes to the page flow to the layout to the navigation to the footer and to everything in between and beyond… everything must be considered. And we mean everything. Not just some of the things. Or most of the things. Or all of the things except that one weird thing that happens in this one screen size... You get the point.
Everything must be considered. Phew.
Join me next week…
The digital landscape is evolving rapidly around us and responsive websites are no longer "becoming a nice-to-have" but rather more "devastating to your business to go without".
If you've already heard enough and just want to start talking to us about your requirements for a responsive website or any of the other services we offer, so that we can help bring real success to your online presence.
Until next week, thanks for your time!
Get in touch about your project
Give us a call or send us an email to talk through your project
Articles in this series
Using Sass and CSS3 Flex as a grid system
3 Apr 2017 We used to be big fans of using singularity to create responsive grids on which to craft our web layouts but we've been converted to CSS3 flex and here's why!
10 lessons from using Drupal 8 + Pattern Lab + Emulsify
22 Aug 2018 The musings of our front end developer after the launch of our first Pattern Lab + Drupal 8 project via the Emulsify base theme.
More recent articles
Are you gambling with the security of your business?
7 Jun 2022 Ignoring security updates will seriously impact your business. It's time to take action.
Why poor web security will damage your business
27 Apr 2022 The consequences of poor web security can be catastrophic so it's essential you have a strategy.