Mobile web design tips: mobile should come first

Mobile first!
A combination of location detection and orientation enables local information to be placed in your current field of vision

I'll just come out and say it: websites and web applications should be designed for mobile first.

For years, most teams did the opposite. Mobile, if it happened at all, was a port of the desktop version that was conceived of, designed and built before anyone even considered the mobile experience.

Expedia desktop

The primary purpose of this page is to let a customer review their travel plans. If you look really closely in the middle of this web page, you may be able to spot this information.

Expedia mobile

In stark contrast, the Expedia iPhone experience puts the same information front and centre and with better visual hierarchy – enabling the user to quickly check arrival and departure times. Gone are all the interface debris, promotions and cruft present on the desktop site. All that's left is what Expedia's users need to accomplish their task. Why couldn't the desktop site do the same?

As another example, consider the difference between the Southwest Airlines website on the desktop and its iPhone experience. Since there are lots of pixels available on the desktop web, they've been filled with lots of promotions, features, options and more – because they can be.

SW airlines

The mobile experience, on the other hand, has a laser-like focus on what customers need and what Southwest does: book travel, check in, check flight status, check miles and get alerts. No room for anything else. Only what matters most.

SW mobile

Focusing on what matters most helps address one of the longest standing issues in web design: the 'everything including the kitchen sink' problem. This problem exists because adding things to a website is relatively easy. Lots of things get added – especially when multiple stakeholders are involved.

Different internal departments, feature owners, businesses and individuals have different requirements for websites. So web teams are often left trying to balance many promotions, interactions, content modules, navigation options and more in a single layout. On a 1024x768 screen there are lots of pixels to fill!

If you design for mobile first, you can create agreement first on what matters most. You can then apply the same rationale to the desktop version of your web product. "We agreed that this was the most important set of features and content for our customers and business" – why should that change with more screen space?

There are of course, differences based on the mobile and desktop contexts. But the core value of a web service remains the same across both formats. When a team designs for mobile first, the end result is an experience focused on the key tasks users want to accomplish without the extraneous detours and general interface debris that litter many of today's websites. There simply isn't room in a 320x480 pixel screen for extraneous elements. You have to prioritise.