What Comes First in Mobile Design: Tasks, Content, or Mobile Optimization?

| 23 min read
645 shares

For many users worldwide, mobile was their first Internet experience and continues to be their primary way to access information. This is also true for people who don't need to use computer desktops, particularly since smartphone applications have dramatically changed how we live our lives. Here, we'll look at three UX approaches to design for a world that relies heavily on mobile to solve problems for entertainment, health, wellness and more. 

© Frank Spillers and Interaction Design Foundation, CC BY-SA 4.0

Distractions surround mobile users. Hence, when you design for mobile, you must prioritize what is important for the user: give them what they need and do it efficiently within their changing environments and contexts.

We can consider three approaches to design interactions for mobile:

  1. Mobile-First: Design for small screen sizes first and then expand to larger device sizes. Users are on the move; they can spare neither time nor attention. Under these constraints (movement, time, attention), decide what makes sense on your screen(s). 

  2. Task-First: Design the core value proposition first. Focus on the users' primary task and support successful task completion.

  3. Content-First: Start with Desirability—what does the user want, need and desire? Design the content around that desire and add the other elements of user experience (interactions, interfaces and usability) afterward. 

Table of contents

What is Mobile-First?

In the mobile-first design approach, you start your design process with mobile users in mind first and then scale up to larger screen sizes. This means you prioritize the mobile experience and ensure all your content and features are accessible on smaller screens. Another way to approach mobile-first is to prioritize content from the outset so that even if you begin your design process on a larger screen, you still have the flexibility to show your content effectively in a mobile environment.

Luke Wroblewski, a Product Director at Google, proposed this concept in 2009 and offered three reasons for designing for mobile first. Here, we've updated Luke's arguments for going mobile first to reflect the new mobile landscape:

1. Mobile Has Exploded

It's undeniable that the use of smartphones has become ubiquitous in today's society. Ensure your app provides an exceptional user experience across different platforms and screen sizes to reach a global audience.

2.  Mobile Forces You to Focus

Regardless of device specifications, the one thing that's key to all mobile devices is portability. People use them on the move, which means that you must focus on the most important actions and tasks for your users.  

There's much more room on a desktop screen, and you can afford to add extraneous features, but smartphones don't give you that luxury. Remember that the user experience on smartphones is also determined by how they're used—on the move and in short, sharp bursts of activity, which is very different from sitting at a desk and browsing the internet for hours on end.

© Interaction Design Foundation, CC BY-SA 4.0

 3. Mobile Offers New Capabilities

On desktop, the web is the standard way to interact with most businesses, but on mobile, the preference has shifted to applications. This is due to smartphones' many sensors and features, such as GPS, accelerometers, pedometers, touchscreens, gesture controls, augmented reality, and eye tracking.

The mobile-first approach enables designers to leverage the full potential of mobile, rather than replicate the desktop experience on a smaller screen.

© Interaction Design Foundation, CC BY-SA 4.0

What Is Task-First?

This approach prioritizes user tasks over other design considerations, such as aesthetics or technical feasibility. This ensures the app is designed with the users’ needs in mind, resulting in a more efficient and practical experience. By focusing on user tasks, designers can also identify pain points in existing workflows and streamline them to improve overall user satisfaction.

For example, let's look at an application like Shazam, designed with a task-first approach. Its primary function is to assist users to identify songs playing in their vicinity. The app achieves this thanks to its clean layout and user-friendly interface that makes it easy for users to complete the main task without any extra distractions or complications.

The Shazam app features a clean interface that helps users accomplish the main task: to identify music playing nearby.

© Interaction Design Foundation, CC BY-SA 4.0

The Task-First approach prioritizes giving users what they want as quickly and easily as possible without requiring them to hunt, search, or think too much.

What Is Content-First?

The concept of a content-first approach has been around since the early days of web design, but it gained new relevance with the rise of responsive design. The basic idea is that content should be the primary focus of mobile UX design, as users come to apps and sites primarily for the content they offer rather than for the interface's design.

As UX designers, we often focus on interfaces and wireframes, but the content-first approach suggests that we should define the content structure first and then add UI and interaction elements later.

There are three stages to this approach:

  1. Copy: Create clear and concise copy that conveys the intended message to users. This may include defining typography, font sizes, and heading structure (H1, H2, H3, H4, H5), which is critical for accessibility. Properly defined headings make it easier for screen readers to parse a page.

  2. UI Elements: Once the copy is defined, it's time to add UI elements such as buttons, icons and graphics that support the content and help guide users through their tasks.

  3. Interaction Elements: Add animations and transitions to enhance the user experience.

© Experience Dynamics, Fair Use

Interested in adopting the content-first approach? Here's a helpful checklist to assist you on your transition. Download the template, and share it with your team!

Get your free template for “How to Use the Content-First Design Approach”
How to Use the Content-First Design Approach How to Use the Content-First Design Approach
Secure form
Please provide your name.
We respect your privacy
Please provide a valid email address.
315,214 designers enjoy our newsletter—sure you don't want to receive it?

Put It All Together: A Demonstration of Mobile-, Task- and Content-First Approach

Now that we've covered the three approaches, let's see them in action! In this video, Frank Spillers will show you how to create an interface for a health app that enables patients to chat with doctors. He'll use examples from each approach: mobile-first, task-first, and content-first.

Show Hide video transcript
  1. 00:00:00 --> 00:00:32

    So, let's apply this kind of  thinking that we've learned: mobile-first, task-first, and content-first. And let's apply it to – I'm just going to choose a random example – say like a patient medical chat with a doctor. And the first thing I'm going to do is I'm going to think, "Well, this is for mobile primarily." So, I could even use  a little whiteboard like this.

  2. 00:00:32 --> 00:01:02

    And I even have some little mini-whiteboards. You can buy little tiny squares that are about the size of a mobile screen. And you can use those to help you focus on mobile. This is more like a tablet format. But what I'm going to do is I'm going to first  of all sketch out my screen. So, I'm going to mobile-first, so I'm going to put the screen there. Because it's mobile, my buttons are going to be really big. Next, I'm going to think, "What's the task?" So, a medical chat, so it's

  3. 00:01:02 --> 00:01:32

    your patient chatting to her doctor. And then the other thing is *content-first*; so, maybe we'll start with content-first, and then as we're thinking about the task and as we're thinking about mobile. The first thing I want to  do is emphasize security. I'm going to put like some kind of lock symbol, that this is like some  kind of secure connection between my doctor and me. And the reason I'm going to do that is because that is compliant with regulations for HIPAA compliance in the US.

  4. 00:01:32 --> 00:02:03

    I might actually show  that my doctor has sent me a message. So, I might have like a message and then have like a number too or something like that. Once the user taps on it, it's going to open the doctor's message. I'll have a note here that this will be like: "Your doctor said this at this time and date." So, I might make a note here, content-first, time, date. And then also make a note whether I've  seen it or the doctor's seen it.

  5. 00:02:03 --> 00:02:32

    And notice what I'm using is essentially a chat mental model of a back-and-forth. But because sometimes there's a lot of story that goes with a medical problem, like you might be describing your small child and the small child may have an existing condition. Things may have happened that you want to tell your doctor. In other words, what I'm trying to say is it's not one sentence.   So, for that, because I'm thinking mobile-first,  maybe I'll maximize to full-screen

  6. 00:02:32 --> 00:03:01

    so that the patient has the entire thing and then when they're done there's going to be a big Send button there for mobile. If I have attachments, because  I'm definitely going to have attachments, I'll have an attachment thing like a picture that they could take, a picture of the child's leg or a health record that they might want to upload  or a link or something like that. I'm going to allow links, so links – okay; attachment – okay. And so, I'm going to have some emoticons on almost like a "How are you feeling?"

  7. 00:03:01 --> 00:03:32

    and I'll just take notes of that: How's the patient feeling? Because in this case I've just made this case like the parent is the user, is the patient advocate. So, how's the patient feeling? And that way I can kind of add some *emotional priority* to the message, because if the doctor knows, for example, that you're happy but you're reporting – you know – something happened, the doctor knows to respond, just like a doctor could tell *in real life*. And a lot of these systems are becoming more mainstream now – you know – where

  8. 00:03:32 --> 00:04:05

    you can video your doctor; and might even add that feature later, might test that with users, where it's like Start Video – if the doctor is online, I might just Start Video, and if there's  a charge, it might say – you know – "Just please know that you're going to be charged (or whatever) for this" or "Your insurance is covered for this." Something to reassure the patient so they're not just hitting the video thing. I might even change that and say Video Request so the doctor has to approve a video call. And that way the doctor can schedule it into her busy week or day or evening or whatever it is,

  9. 00:04:05 --> 00:04:30

    so that the patient's not on demand, like FaceTiming – you know – and creating problems. Thinking about that, how that content scales, how the user can go full-screen; also how they can potentially search, so I might add that as a note. I want to have a search here, search messages. There's going to be a lot of these. There might be dozens. You think of a chronic patient

  10. 00:04:30 --> 00:05:01

    – you know – a care situation could go on for years. I want to have saving of attachments. I want to also be able to edit. So, I might add a note there that there's  going to be an edit of – I'm going to really make a lot of desirable stuff just kind of off the top of my head. But normally I would do user research, trying to understand patient-doctor communication, talk to doctors, talk to clinicians, to nurses, nurse practitioners, and talk to patients – and not just the patient themselves,

  11. 00:05:01 --> 00:05:30

    but the *patient advocate* like a parent who's looking after, for example, their parent or grandparent or a child or somebody with a disability, and have a way for them to edit conversations, to make sure they're private. If privacy or security comes up as a top concern, I might add an *extra layer of security* which we just don't see in our apps. Things with patient records – some conversations might not matter. There might be some very, very sensitive material.

  12. 00:05:30 --> 00:06:01

    In the healthcare world, they talk about trauma-informed approaches, and so we kind of maybe need to start bringing that to our app strategy as well. So, I hope that gave you some example of how to kind of blend a mobile-first approach – you know – big button, small screen, a task first: what does the user need to do? "Has my doctor come back to me yet? Is there a new message that I can reply to?" But then also what makes it desirable? You know – what content is important to include there?

  13. 00:06:01 --> 00:06:27

    And really in a content-first approach, I might lay it out. I might start with just the message, and then think about just the message. You know – instead of writing the Chrome, I might just focus on the message and all the things that I mentioned that I might add to the message. I might think about making that experience as pleasant and as comfortable and as safe as possible, and that could be like in a content-first approach.

The Take Away

It's important to understand the unique challenges and opportunities of the mobile platform. Here are three powerful prioritization approaches to keep in mind:

Mobile-First: Mobile-First is a design strategy that puts mobile at the forefront of the design process. It recognizes the importance of the mobile web and emphasizes the need to create an experience tailored specifically to mobile devices. 

Task-First: Task-First prioritizes users' tasks. It helps them complete tasks quickly and efficiently and minimizes cognitive load. This approach is particularly well-suited for mobile devices since users are often on-the-go and need to complete tasks quickly.

Content-First: Content-First puts content at the center of the design process. Rather than starting with wireframes or UI elements, this approach begins by defining the content structure first. This allows designers to optimize experiences for different contexts, physical or otherwise.

References and Where to Learn More

Read Luke Wroblewski’s original proposition for Mobile First.

See Clayton Lewis and John Rieman’s original definition of task-centered design in Task-Centered User Interface Design: A Practical Introduction.

More about content first in these articles:

To know why the heading structure is crucial for accessibility, see this resource:
Accessibility at Penn State 

Read the forecast number of mobile users worldwide from 2020 to 2025, from Statista.

Hero Image: © Interaction Design Foundation, CC BY-SA 4.0

Get Weekly Design Insights

Join 315,214 designers who get useful UX / UI Design tips from our newsletter.
A valid email address is required.
645 shares

Open Access—Link to us!

We believe in Open Access and the democratization of knowledge. Unfortunately, world-class educational materials such as this page are normally hidden behind paywalls or in expensive textbooks.

If you want this to change, , link to us, or join us to help us democratize design knowledge!

Privacy Settings
By using this site, you accept our Cookie Policy and Terms of Use.

Share Knowledge, Get Respect!

Share on:

or copy link

Cite according to academic standards

Simply copy and paste the text below into your bibliographic reference list, onto your blog, or anywhere else. You can also just hyperlink to this article.

Interaction Design Foundation - IxDF. (2023, June 1). What Comes First in Mobile Design: Tasks, Content, or Mobile Optimization?. Interaction Design Foundation - IxDF.

New to UX Design? We're Giving You a Free eBook!

The Basics of User Experience Design

Download our free ebook “The Basics of User Experience Design” to learn about core concepts of UX design.

In 9 chapters, we'll cover: conducting user interviews, design thinking, interaction design, mobile UX design, usability, UX research, and many more!

A valid email address is required.
315,214 designers enjoy our newsletter—sure you don't want to receive it?