Building a Mobile-optimized Website
I recently noticed an interesting article on the Globe and Mail website about guiding design principles to Building a Mobile-optimized Website and I have re-published it below for your convenience.
A few years ago, building a mobile-optimized website went something like this: Take your regular-sized desktop site, and squeeze. The result was mobile websites that were hobbled versions of their bigger, better desktop counterparts. From a design standpoint, mobile devices were second-class citizens. Spurred on by the growing popularity of smartphones and tablets, an increasing number of businesses are building mobile-optimized sites first, then scaling things up for laptop and desktop visitors.
Earlier in this Web Strategy series, we looked at why a “mobile first” strategy is worth pursuing now, and which types of businesses benefit most from going mobile. This instalment offers a look at some guiding design principles that businesses should keep in mind when adopting a “mobile first” website strategy.
“Mobile devices, by virtue of being mobile, have to be portable. They have to fit in your pocket or purse,” says Luke Wroblewski, a Silicon Valley-based Web design strategist, entrepreneur, and author of Mobile First
“As a result, the screens are very small,” says Mr. Wroblewski, who co-founded Bagcheck, which was acquired by Twitter Inc.
For example, the average smartphone screen has about 80 per cent less available space than a standard desktop Web browser. To get a sense of the difference, try testing your existing website with a tool like Google’s GoMoMeter. Designing for “mobile first” means making important decisions about what to include, and what to leave off of a smaller screen. “The sheer physics of it require you to rethink what’s really important on a site,” says Mr. Wroblewski, who thinks smaller screen sizes should be seen as a positive design constraint that can benefit both mobile and desktop design. If your mobile site includes simple navigation and minimal clutter, those same principles can be applied to your desktop site as well.
Rather than shrinking your existing desktop website to fit a smaller screen, designing a mobile site from scratch should involve a winnowing process. Mr. Wroblewski suggests distilling your mobile site down to features and content that “provide immediate value to your customers, and ultimately your business.”
On the mobile Web, milliseconds matter.
“Study after study shows that hundred-millisecond delays in the loading of Web pages can cost companies huge amounts of revenue and engagement,” Mr. Wroblewski says. Indeed, in 2009, Forrester Consulting found that “40 per cent of consumers will wait no more than three seconds for a Web page to render before abandoning the site.”
Speed is especially important for mobile visitors who go to your site over a Wi-Fi or cellular data connection. These connections, though ubiquitous, aren’t always as reliable or robust as the high-speed, wireline network connections in homes and offices. Free tools like Yahoo’s YSlow and Google’s PageSpeed can analyze your mobile site and suggest changes to improve speed. Designing for speed on mobile devices can pay off on the desktop, too. “If you make it fast enough for mobile, it’ll be blazingly fast on big pipes on a desktop,” Mr. Wroblewski says.
Make use of expanded capabilities
Mobile devices often have hardware features that aren’t present in most desktops and laptops – such as GPS, accelerometers, gyroscopes, and touch screens. Increasingly, mobile browsers are gaining access to these hardware features through Web standards like HTML5. Depending on the device, your website may be able to make use of a user’s camera, GPS location, or other information like device orientation.
When used effectively, these additional features can help you build a mobile experience that goes beyond the point-and-click paradigm of desktop Web browsing. When your website becomes location-aware, or can understand how a user is holding a device, it becomes possible to create richer, more engaging mobile experiences. However, Mr. Wroblewski cautions that support for these types of hardware features varies significantly across devices. Just because a smartphone has GPS functionality doesn’t necessarily mean your website will be able to make use of it (Mobilehtml5.org has a useful rundown of mobile devices and the capabilities they offer to websites).
“The devil is really in the details there: testing to see if a capability is available, and making sure it runs smoothly,” Mr. Wroblewski says. The “mobile first” design strategy represents a significant departure from the past two decades of Web development. Smartphones and tablets fit into our lives in different ways than laptops and desktops, and developing for them requires a different kind of thinking. For Mr. Wroblewski, a successful “mobile first” strategy requires a deep understanding of the devices themselves – “understanding the circumstances and the environment of use, understanding the capabilities of these devices, and understanding their constraints,” he says.