Mobile First is starting to achieve a buzzword like status, much in the same way that web 2.0 and HTML5 did. And that’s a shame, because mobile first is actually really awesome.
Today, I want to cut through the crap and explain mobile first in plain, practical terms.
Ubiquity & Diversity
Right now is an insanely exciting time to be making things for the web. Internet access is virtually ubiquitous, and for a large and rapidly growing percentage of people, the internet is something you rarely or never access on a computer.
Obviously, people are browsing the web on tablets and smart phones. But they’re also browsing on gaming consoles like X-Box and Gameboy, on web-enabled TVs, and on older or not-so-smart phones. I’ve even heard of folks using the Kindle e-ink browser to do things like send emails and read on the web.
Screen sizes, device capabilities, and user contexts all vary wildly. Your job is to make sure everyone who wants to can access your content.
Responsive Web Design
Over the last couple of years, Responsive Web Design (RWD) has emerged as a way to deal with the growing device diversity.
Rather than building a separate mobile site, your existing design “responds” to device that’s accessing it, adjusting to accomodate the user. Content shifts and flows. On a small screen, the site may be a single column. On a big desktop monitor or TV, it can be many columns wide. On tablets, somewhere in between.
The more nitpicky folks in the web community will tell you that Responsive designs need to have fully fluid columns, while fixed-width columns that simply move or stack on top of each other are called Adapative design. It’s generally agreed upon now that Adaptive is a type of RWD.
The goal, however, is always to provide the same content regardless of the device.
Mobile First is a type of Responsive Web Design
Responsive Web Design isn’t always mobile first, but Mobile First is always Responsive.
Many RWD approaches use what’s known as graceful degradation. With this approach, you build your normal “desktop first” design (often a 960 pixel or so grid), and then use media queries to set maximum widths below which content shifts and reflows. The previous layout for this site used that approach.
The problem with this approach is that not all mobile devices are smart phones. They’re not all very fast or capable. They sometimes don’t recognize media queries. And so that beautiful bit of “content choreography” you use for mobile sites? They’re not seeing it.
Enter Mobile First.
Don't gracefully degrade. Progressively enhance.
Mobile First takes the opposite approach of graceful degradation. Instead of building a desktop site and retrofitting it to mobile devices, you build a really simple foundation and then add features for devices that can support them.
They’re not always beautiful, but they’re functional.
It's not just looks
You can’t design mobile first without caring about web performance. Your content is being accessed on weak cell phone signals, not just high-speed broadband.
This doesn’t just benefit your mobile users. It benefits everyone. No one likes a slow website.
I’ll be honest: I don’t sit down and sketch out the mobile layout before I sketch the desktop layout. It’s more fluid than that.
I usually sketch them both out at the same time, and one design feeds the other. But the important thing is that you’re always thinking about how to the design would work on a tiny flip-phone in the middle of the desert.
To see a very simple Mobile First site in action, download my Go Mobile First WordPress them and start poking around under the hood.