Monthly Archives: July 2013

Book Review: “Mobile First”

“Mobile First” by Luke Wroblewski is a great introduction to designing web experiences that cater for both desktop and mobile devices. With a large number of people accessing the web on their mobile devices, “Mobile First” is all about designing user experiences beyond the confines of the desktop.

Naturally, there’s likely to be overlap between the design of native mobile applications and mobile first or responsive mobile design, where a desktop product is created with the mobile experience at the front of mind. In this book, Wroblewski focuses on creating basic websites which can be easily enhanced for mobile (i.e. smartphone and tablet) and PC. These are the main things I learned from reading “Mobile First”:

  1. Common constraints of Mobile First – The main constraints of designing for a mobile experience are (1) screen size, (2) performance and (3) time and place. The main point that Wroblewski makes with respect to all three constraints is that when designing for mobile one really needs to know his users and his business. It isn’t good enough to simply try and make your existing website work on a mobile phone; Wroblewski argues that “if you design for mobile first, you can create agreement up front on what matters most. You can then apply the same rationale to the desktop (and any other) experience of your web product.” A good example is Flickr’s mobile web experience which reduces 60+ navigation options on the Flickr website to 6 (see Fig. 1 below).
  2. Capabilities of Mobile First – Wroblewski outlines how you can use mobile device capabilities like camera, location detection and accelerometer to innovate (simple) use cases. Mobile opens up numerous new ways to meet people’s needs. However, one shouldn’t overlook browser limitations and the constraints these can impose on your mobile experience! It was also interesting to read about the 3 critical, common mobile interaction types as identified by Josh Clark (author of “Tapworthy”, see Fig. 2) which are reflected in Google’s breakdown of mobile users (see Fig. 3).
  3. Content over navigation – Whereas the more ‘traditional’ websites can be quite navigation heavy, one of the key principles of Mobile First is “content over navigation.” Wroblewski’s main advice is to start the conversation with users through content rather than navigation. YouTube and ESPN’s mobile web experiences are good examples. In both cases,  the navigation options have been reduced and simplified (see the example of ESPN in Fig. 4).
  4. Touch and “Going small by going big” – Having touch devices means using your fingers to interact with a site or application! Wroblewski therefore stresses the importance of creating appropriately sized and placed actions (‘touch targets’) to help people tap with confidence and accuracy. As an example, the book mentions Quora’s mobile web login screen as an example of where the key actions are quite small and placed closely together (see Fig. 5) which bears the risk of carrying out the wrong action.
  5. Designing for different mobile devices – I was pleased to see that Wroblewski addresses the design and implementation issues around constantly changing mobile devices, browsers and operating systems. I guess the key point here is that with responsive web design you can set a baseline mobile experience first and adapt your layout as device capabilities change. This tends to be referred to as “fluid layouts” whereby interface elements like search are designed in such a way that they adapt to the space available to them. A good example is the fluid layout used for Google Places which adapts to different screen widths available.

Main learning point: “Mobile First” is an easy to read book on responsive web design. Fortunately, the book doesn’t spend too much talking about the pros and cons of native vs responsive mobile design. Instead, Wroblewski explains the main principles and benefits behind a mobile first design approach, without closing his eyes for some of the potential pitfalls and risks involved. Even though “Mobile First” sometimes gets a bit too technical for my liking, the book does a great job in getting designers and non designers to think more about designing with mobile in mind.

Fig. 1 – Flickr’s mobile web experience


Fig. 2 – Three critical, common mobile interaction types (from: “Tapworthy” by Josh Clark)

1. Micro-tasking

2. “I’m local”

3. “I’m bored”

Fig. 3 – Google’s breakdown of mobile users (as adapted from Timo Elliott’s great blog post)

1. Repetitive now – The user who checks the same piece of information over and over again (e.g. the weather forecast)

2. Urgent now – A request to find something specific fast (e.g. directions to the airport now)

3. Bored now – Users who have time on their hands (e.g. on their commute)

Fig. 4 – ESPN’s mobile web experience, a good example of “content over navigation”

ESPN mobile experience

Fig. 5 – Quora’s mobile web login screen where the main actions are quite small and are placed closely together


Related links for further learning:


Tags: , , , ,

Book review: “Microinteractions: Designing with Details”

Interaction designer and author Dan Saffer recently published a book called “Microinteractions: Designing with Details”. As the title clearly suggests, this book is very much about those small interactions which make up a product or a feature. In fact, Saffer’s book is very much inspired by a quote from the famous American designer Charles Eames who believed that “The details are not the details. They make the design.”

“Microinteractions” is a very practical book in which the principles behind designing effective microinteractions are well explained and illustrated. These are the main things I learned from reading “Microinteractions”:

  1. Doing a single thing (and doing it well) – Saffer defines a microinteraction as “a contained product moment that revolves around a single use case.” It’s about creating functionality that does one thing (and does it well), and microinteractions are typically not meant to be standalone features. Examples of microinteractions are accomplishing a simple task, adjusting a setting or connecting devices together. Saffer stresses the need for microinteractions to be simple and effortless.
  2. The different parts that make up a microinteraction – In “Microinteractions” Saffer breaks down the different parts that form an microinteraction: (1) the trigger which initiates the microinteraction (an example is the iPhone “eject” button in iTunes, see Fig. 1) (2) the rules which determine how it functions (3) the feedback that the rules generate (an example is YouTube’s favicon which changes dependent on the status of the video being played, see Fig. 2) and (4) the loops and modes that make up the meta-rules of a microinteraction.
  3. Start with user need (and restrain yourself) – If anything, “Microinteractions” serves as a good reminder of the importance of starting your designs with an understanding of user need: what does the user want to accomplish? When do they want to do it? How often? This focus on user needs is one of the reasons why Saffer urges his readers to apply constraint when it comes to designing microinteractions. He states that designing microinteractions is all about “doing as much as possible with as little as possible.” I’ve included some examples of well designed microinteractions referenced in the book in Fig. 3 below.

Main learning point: “Microinteractions: Designing with Details” is an incredibly helpful and insightful book. Dan Saffer writes in a concise but practical way, making the reader think about user needs and how to translate this into microinteractions that help user accomplish their goals. The book is one of the best design books I’ve read in a while and I’d recommend it to anyone with in an interest in design or human interaction. Even if you don’t end up reading the book, at least have a look at the very helpful microinteraction framework that Dan Saffer has developed (see Fig. 4 below)!

Fig. 1 – The iPhone “eject” button in iTunes (from:

iPhone eject button

Fig. 2 – YouTube’s favicon changes based on whether the video is buffering, playing or paused (from:

YouTube feedback loop

Fig. 3 – Good examples of well designed (and restrained) microinteractions

Gmail warning

Gmail warns the user when he starts chatting with a user outside his organisation (from:

Evernote microinteraction

The Evernote Web Clipper button will automatically convert to gray and will be disabled if the extension is already installed in the browser (from:


The “Follow” button changes to “Follow back” on Mixcloud if the user is already following you (from:

Fig. 4 – Microinteractions framework as included in “Microinteractions: Designing with Details” by Dan Saffer

microninteractions framework


Tags: , , , ,