Sometimes, a responsive web design is not the most appropriate way to develop a companyâ€™s mobile presence. There, I said it. Recently, all the talk is about responsive design â€“ justifiably for the most part; it is a genuinely significant change for a lot of clients who now need to consider how and where their websites are viewed, beyond the desktop. And for web designers itâ€™s probably the most significant change in development practices since we all decided that HTML and CSS were a better way to build sites than Flash. But itâ€™s not always appropriate.
A recent case in point is the work Iâ€™ve been doing for Momentum Events. Itâ€™s a big WordPress site with a lot of custom plugins, a lot of content, a lot of assets (PDF downloads, etc.), a lot of traffic, and a good number of mobile users.
We took the decision to design & develop separate desktop and mobile sites. In this way, we would serve up code bases that were substantively different from each other (something made straightforward with WordPress and the addition of the excellent â€˜Any Mobile Theme Switcher Proâ€˜ plugin) and provide tailored user experiences as a result.
But why? Why didnâ€™t we do the same thing â€“ but with a responsive design?
Well, okay, we could have. Mostly. But hereâ€™s the thing: pages are big, and mobiles are slow. The home page for Momentum has 22 images on it – most of them are â€˜lazily loadedâ€™ so they donâ€™t exert a page weight immediately â€“ i.e. they donâ€™t impact download time of the page â€“ but still, on a mobile device, thatâ€™s going to slow the site down considerably. (A common mistake when developing for mobile is assuming that everyone everywhere has a decent connection. Well, Iâ€™m in rural Ireland, my client is in Manhattan – I can tell you this: we have very different expectations of our mobile network speeds!)
Additionally, the home page connects to LinkedIn, Twitter, Facebook and Google Plus. Thatâ€™s a lot of external connections that we donâ€™t have control over. Again, these will be loaded in such a way as to not impact the download of the home page â€“ but on a mobile device, theyâ€™ll potentially create a â€˜stutteringâ€™ experience whilst the connections are made.
A page size of a few Mbâ€™s is not ideal on a desktop browser – but on a mobile browser it becomes downright irresponsible. AsÂ Brad Frost points out:
One of the biggest challenges of creating responsive web designs is the balancing act of delivering a full experience while still maintaining a snappy user experience across the board
Across the board, only 3% of small screen versions of websites are significantly lighter than their desktop equivalents. Thatâ€™s not good.
But yes, we could have developed our site to be within that 3% (and given ourselves shiny apples and gold stars as reward). But still â€“ we chose a dedicated site.
For us, it came down to context and relevance in the end. Our feeling was that â€“ for business users looking to find out about business conferences â€“ we wanted to present different information â€“ information that was more relevant â€“ in a mobile context. So, the home page of the site for the desktop version talks about â€˜big pictureâ€™ things (mission statements, business partners, company brochure) as well as the events themselves – but the mobile version of the home page â€“ thatâ€™s all about the events. Just a simple list of events that makes it super easy to get right into the guts of the content.
A dedicated event page of the desktop version â€“ again, that has a richer experience for the user: speaker photos, connection information, twitter stream, LinkedIn Group information, and so on. The mobile version of the same page is much much lighter â€“ and arguably more focussed.
However, if you want to serve up substantively different content to different devices then perhaps a dedicated mobile site is the way to go after all. You can achieve it quite readily, without a lot of the attendant headaches you may get when attempting the same effect responsively.