I’ve just finished reading through The Mobile Book by Smashing Magazine. The book is a fully packed 334 pages of analysis on the current state of mobile and best responsive design practices. Writers include gurus such as Peter-Paul Koch, Stephanie Rieger and Brad Frost.
Bottom line: most people working in web design today should probably read this book, whether they’re designers or developers. The book has useful data on today’s mobile landscape, discussion on how to bake responsive design into our processes, the peculiarities of designing for touch and instructions on how to optimize for mobile.
From the foreword (by Jeremy Keith):
There will come a time when this book will no longer be necessary, when designing and developing for mobile will simply be part and parcel of every Web worker’s lot. But that time isn’t here just yet.
Here are my six key points I gathered from the book:
The Internet of Things is a thing, and is likely to explode in the near future with more Internet-connected devices entering the market that are neither traditional mobile devices nor desktops or laptops. Some don’t even have screens.
Responsive design that focuses only on screen size can result in huge downloads on mobile. We need to pay more attention to conditional loading of secondary content.
Creating detailed Photoshop comps of web sites can set false expectations to clients and other stakeholders. Responsiveness should be part of the design process very early on.
The capabilities of mobile browsers vary wildly (especially on Android), and browser/device detection is increasingly a necessary evil. RESS (Responsive design + server-side components) and server-side libraries like Detector (by Dave Olsen) are a possible solution.
With new hybrid touch-enabled devices, we are less likely to be able to predict whether the user can use touch as an input method. Due to this we need to optimize for touch by default.
Touch interfaces take web design into the realm of industrial design. It’s no longer just about how things look and behave, we also need to consider how people hold their devices. This has significance when deciding where to put key controls.
Regarding point 2 in my list: I’ll be presenting a simple example on how to use conditional loading for any content in WordPress in an upcoming post. The same method is used on this site to load the sidebar. Edit: it’s now online, see Simple Conditional Loading in WordPress.
Some years ago browser testing meant just testing in Firefox, Safari and possibly Opera, and cursing and testing in IE6. Good standards support in current browsers has made development easier on one hand, but more complex than ever on the other hand with the demands of responsive design, the rise of mobile and websites themselves becoming more advanced.
Now on the desktop we have to worry about Chrome, Firefox, Safari, Internet Explorer 7,8,9 & 10, and on ‘mobile’ there’s at least Safari for iOS (phone and tablet), Windows Phone, multiple versions of the Android Browser, Chrome for Android, the BlackBerry Browser, Firefox, Opera Mobile and Opera Mini.
This post describes a snapshot of my current browser test setup and it’s the third part in my “web dev on Mac OS X” series. The first two were about utilities and web development apps. I’ll try to keep this series of posts up to date as the tools of the trade change.
Latest versions of Chrome, Firefox, Opera and Safari
You should of course have all the latest versions of the most popular desktop browsers. Ideally it would be a good idea to have older versions too, but since both Firefox and Chrome update themselves automatically, this is not much of an issue (see Arstechnica’s browser share analysis from last October)
Since Firefox 3.6 was the last version not to be updated automatically, I like to keep it around, since it has quite a few issues with some HTML5 elements and CSS3. An easy way to install an old version of FF alongside the current version is via portableapps.com.
Internet Explorer 7, 8, 9 & 10 in VMWare
Internet Explorer testing is annoying, because installing multiple stand-alone versions of IE is difficult, and in some cases impossible. I currently have a VMWare virtual machine running XP with IE versions 6,7 and 8, installed using Multiple IE. Unfortunately this setup is somewhat buggy, but it works. I have a separate Windows 7 and 8 VM’s running IE 9 and 10 respectively. This can get messy and requires a lot of HD space. Also, testing local websites requires editing the hosts file of each VM.
Testing on real devices is essential, and at least before going live I try to test on as many devices as possible. Since my own collection is limited (Android, iOS and S60) and there’s no open device lab near me, I occasionally visit the local department store and try out all the phones on display. Necessary, but not very practical for quick debugging.
Adobe Edge Inspect
For devices that support it (ie. Android and iOS), Adobe Edge Inspect is a great time saver. Basically it allows you to browse the same site synchronously on your desktop and your mobile via a mobile app and a browser extension. Even Edge Inspect doesn’t allow browsing local sites though, and that’s where the next solutions come in.
Opera Mobile Emulator
The Opera Mobile Emulator is an excellent and easy way to test a responsive web site in a huge number of different sized displays. It’s a useful tool whether your users use Opera or not.
The free Mac OS X Developer Tools include an iOS simulator, which is at least 99% identical to the actual devices (iPhones and iPads). The emulator allows rotating the device, simulated shakes etc. This is probably the mobile testing tool I use the most.
Going forward: Remote virtual machines with Browserstack
Maintaining all these emulators is messy, to say the least. So I’ve been eyeing Browserstack, which allows testing in IE 6-10, recent versions of Chrome, Firefox, Opera, and best of all, emulators of most Android & iOS devices of significance. From my point of view the only thing missing is Windows Phone. Oh and Symbian would be nice too.
The interface is really easy to use and straightforward. You input the address you want to test, choose an operating system and browser, and that’s it. Using a remote desktop via a browser is of course fairly slow, but the really killer feature of Browserstack is the ability to test local sites (like testsite.dev). This often makes Browserstack more convenient than the alternatives.
Browser testing is a complicated business, and your needs will depend on the type of site you’re developing and user demographic. Testing in more than one browser is a start, but mobile testing has also become a must. In a year or two it might even be more important than desktop browser testing, if it isn’t already.
Testing on a real device gives a good feel to the restraints of that device, but remember your iPhone/Samsung/Nokia model isn’t the only one out there. As more and more varied devices enter the market and testing needs get more complex, tools like Browserstack are likely to be the only realistic testing option for the vast majority of designers and developers in the future.
Responsive design shouldn’t be just about checking screen width and removing stuff on mobile devices, even though this is what it often amounts to. I also admit to doing this myself. Designing with a mobile first approach is sensible, but we run into problems with the typical wireframes/photoshop/html pixel-perfect workflow.
Stephanie Rieger made this excellent presentation on pragmatic responsive design with lots of good points.
The iStat App from Bjango is one of the many cool reasons for having an iPhone. In addition to giving system stats of the device itself (not so interesting) it enables easy monitoring of remote servers. There’s a free server app for those with a Mac server they want to monitor, but most interestingly they have a command-line app for Linux and Solaris.