There’s been a lot of buzz on the internet recently about “responsive” websites. I’m sure you’ll be aware… (if not, skip ahead to the examples below and then come back here!) – but what does it actually mean for clients and developers? Well put simply, a responsive website is one that will automatically adapt to any screen resolution or device (i.e. mobiles and desktops). Ever looked at a website on a mobile phone only to find it looks different when viewed on a desktop? There is a good chance that a responsive design was used to develop it (these websites can also be produced using other methods, but that’s another blog entirely!).
Now for the technical bit. Responsive layout is implemented using CSS3 “media queries” (stay with me) – put simply, a set of “if” statements that go something like this:
@media only screen and (max-width : 600px) { /*Your styles go here*/ }
In plain English this means “if the device you’re viewing the website on is less than 600 pixels wide, do these styles“. And that’s pretty much all there is to it from a development point of view – from here, the development time largely depends on the complexity of the design.
Word of caution though – a responsive design is something that really needs to be thought through (and agreed with the client!) right from the beginning of the web design and build project i.e. before the design stage. It’s no good having a site developed, then a year down the line asking the developer to “make this responsive”. In some cases, this might be possible, but it is obviously better (and more cost-effective) to develop it from the start. This may all sound great – a website that works on any device, but there are some downsides to responsive layouts – I’ve outlined a few pros and cons below.
Pros:
- Your website will still be fully usable regardless of screen resolution
- One website that works on any device (mobiles, tablets and desktops)
Cons:
- Takes additional development time (i.e. cost!) to implement
- Loading times – even if elements of the website are hidden through CSS, they exist in your markup (i.e. HTML), therefore they are still loaded regardless of visibility resulting in wasted bandwidth.
- Ideally needs to be thought about from the very beginning – can be tricky to implement in an existing website
- Requires the Designer to be aware of how elements of the website will ‘shift’ according to size of the browser. Not necessarily a ‘con’, but your designer must fully understand and be able to implement (training may be required!)
You will notice that I have listed more cons than pros, but the two ‘pro’s are really big ones. Having your website automatically adapt to work and be fully usable on pretty much anything will not only show clients that you are fully up-to-date with the latest technology, but will also mean that your websites could still look great even on devices that aren’t out yet!
If everything I’ve said above has given you a headache, have a look at the examples below (ideally on different devices) to demonstrate graphically what I mean:
- http://www.smashingmagazine.com/ – Probably the best example of responsive design around (from a development point of view)
- http://css-tricks.com/ – Another very clever example – I particularly like how the character (top right) changes depending on browser width!
- http://webdesignerwall.com/ – Simpler than the previous two, but still works well
- http://www.anderssonwise.com – The inner content pages are relatively simple, but try viewing the homepage on different devices.
Notice how the layout changes depending on which device you view it on? You can also replicate this effect by resizing your browser window if on a desktop computer. That’s pretty much the basics of responsive layout!
James Wills, Digital Developer






