Posts Tagged ‘usability’

10 Mobile Usability Testing Tips

Thursday, February 3rd, 2011

Years of mobile testing have led to a number of items that we, as user experience researchers, consider whenever we set out to conduct a test that takes place on a mobile device such as a personal phone or iPad.

In somewhat more typical test, participants will arrive at a lab and use a generic PC for the task at hand. With mobile testing, however, often the participants are asked to bring their own phone with them so that we can see how they interact with the subject using their own device. Of course, we’ve conducted plenty of studies using proprietary subjects, and in those circumstances, the participants use a ‘control’ device. Those tests are easier since you eliminate the issues that inevitably appear when participants are asked to bring in their own device.

With that in mind, and in no particular order, here are ten tips to consider when testing a website/app on a mobile device.

1. Have a backup plan – This includes a backup plan for participants, devices, and location. We’ve seen it all. The participant forgets to bring her phone. Or, he dropped his phone on the way to the study and the screen cracked. Maybe reception is bad for a certain carrier in the particular location that you are conducting sessions. All of these things can, and will, thwart your study. Trust me, I’ve seen them all happen. By assuming things will go wrong, and creating a backup plan, you can salvage almost any situation.

2. Test reception ahead of time – Before conducting the study, you should have an idea of which devices you want to test. Based on this information, do yourself a favor and sit in the room that you plan to have sessions, pull out your phone, and see what kind of reception you get. Now, get a hold of someone with a phone for each type you intend to test and repeat this process.

As a backup plan, make sure that a strong wifi network is accessible. Cell reception is notorious for dropping bars at the exact moment your session starts. Being able to quickly switch to wifi in order to carry on is important.

3. Do your homework – Some of our clients have an idea of which devices they would like to test but there are so many variations that sometimes it is difficult to be totally prepared. Doing your homework can help. For instance, one study we conducted focused on smartphones like iPhones and Android. However, our client wanted to test a few phones that fall somewhere between a smartphone and a feature phone. By working closely with our recruiter, we were able research certain models to see if the participant’s phone would be a good match.

Another good option for doing your homework is to use a virtual testing environment. Products like MITE (Mobile Internet Testing Environment) by Keynote (Disclaimer: Keynote is an AnswerLab client) provide you with an array of virtual devices which make it easy to pull up a website and see exactly how it will appear on that device.

4. Pilot test – At least a day before your first session, and hopefully sooner, conduct a pilot session. It’s best if you treat the pilot exactly like a real session so that you can find the problem areas before you actually bring in real people for testing. If you neglect all the other tips in the article, this is the one to keep. Conduct a pilot and you won’t regret it.

5. Record make/model – Even if our client doesn’t ask, we always record the make and model of the participant’s device. Either have your recruiter do it or take a moment at the beginning of each session to capture this information. It comes in handy, especially for design teams, when something unexpected happens during the test.

6. Bring phone/charger – Instruct your participants, in big, bold letters, to bring their phone and charger to the session. And then tell them again. And once more for good measure. Despite this, at least one of your participants will arrive without their phone. Or their phone will have 10% battery left. I guarantee this will happen during your mobile study.

7. Plan for screenshots – How are you going to capture screenshots for your report? On desktops, that’s simple. For mobile devices, it can be quite a challenge. iPhones, for instance, make it easy to grab screenshots. Androids, on the other hand, do not.

8. Ask questions about site/mobile site/apps in pre-interview – I’ll often include some line of questioning in the pre-interview to understand the participant’s comprehension of full website, mobile websites, and mobile apps. I have found that many participants struggle to articulate the difference between them. Though it may not be pertinent for your study, I think it is easy information to capture and gives my clients a better understanding of consumers.

9. Turn off ringer. Don’t answer texts, etc. – Just like they do at the movie theater, tell your participants that you require their undivided attention during the study. Have them turn off their ringer and encourage them to dismiss texts. Remember, mobile devices are extremely personal and people are used to reacting to any alert, in the moment.

10. Figure out how you are going to record the session and allow clients to observe. This can be a complicated and sometimes costly affair. Simple solutions are often best but every study requires it’s own solution. In another blog post, Image Capture Devices, we discuss some options that might help you sort out the best solution for your needs.

In the Lab: Image Capture Devices

Monday, October 4th, 2010

We conduct a lot of tests at AnswerLab. We test websites, mobile apps, paper prototypes, wireframes, software, and more. For some stimuli, such as a website, capturing the computer screen for observers to see and record is easy. For that we usually rely on Morae Recorder and some kind of streaming solution such as WebEx or GoToMeeting.

Certain stimuli such as paper prototypes and mobile interfaces require creative capture solutions. We’ve used the Noldus Mobile Device Camera, hired videographers, hacked iPhones to display on a computer screen, and used document scanners such as the WolfVision Desktop Visualizer to capture a session.

There are pros and cons to each solution of course. The Noldus requires just the right lighting, videographers are an added expense and require the participant to remain in a somewhat fixed position, and sometimes hacking an iPhone isn’t suitable for the study.

We’ve had good success with the WolfVision VZ-9plus³, especially for paper prototypes and mobile devices. With a large range, the participant has an easy time keeping the stimuli in view. Auto-focus is handy and the number of video in/out ports allows the session to take on a level of sophistication that is often difficult to plan and execute.

For instance, suppose your participant is interacting with a website on a computer in the lab. That computer is plugged into the WolfVision and the observers in the back room are intently watching what is happening as the user interacts with a website. Now, imagine that the designers also wanted to get some feedback on a few paper prototypes during the last ten minutes of the session. No problem, just lay the paper down on the WolfVision’s viewing area, press a button to send the image to the backroom, and your observers are instantly seeing the participant as she interacts with the paper prototype.

Switching from a digital to paper stimuli and sending the image to the backroom is not usually this easy, as any researcher knows.

As I mentioned, each solution has its advantages and disadvantages. The WolfVision has its place but one must pick the right tool for the job. At AnswerLab, we are fortunate to have a plethora of tools at our disposal and picking just the right one for the job is one of our specialties.

Conversation with a website

Friday, September 17th, 2010

I’ve come across this video which pokes fun at ‘difficult’ websites. It’s funny… and it’s true. Take away for the day: make sure that your user can perform core tasks from the landing page.

Favorite quote:

I can’t go back. That’s not how it works – I need to show you all your options or you might miss what you are looking for.

Emerging iPad Best Practices: App Navigation

Monday, August 9th, 2010

In May, we conducted our first series of usability research sessions with the iPad. The research spanned 5 days for a total of 25 participants, and very quickly we saw certain navigation patterns emerge. Participants consistently struggled with certain apps, while other apps were much easier to use and navigate.

This post will outline a few of the best practices that we have synthesized from our early research. AnswerLab has also published a full report that tackles the question: How can content owners and digital marketers successfully create a digital content strategy across mobile platforms? See our website for more information about iPad user experience research.  

1. Don’t neglect information-seeking paradigms

Users have been conditioned by years of web-browsing to expect certain navigation elements. For example: Participants in our test were frustrated when they could not find a way to go Back or return to Home.

Confused, some of these participants used the iPad’s own Home button, thereby inadvertently exiting the app completely. This disrupted the flow  and took the users out of the immersive experience of the app, making them less likely to return again.

Users struggled to find their way back to the app home screen in Pinball HD for iPad.

Many participants also felt disappointed to learn they could not search content in the New York Times Editor’s Choice or NPR apps. They said that the inability to search diminished the utility of the app to the point that they would use the website instead of the app going forward.

The takeaway? Provide a simple, discoverable way to go Back or get to the app’s Home screen easily. And if your app contains a lot of content, make sure your users have their preferred method of wading through – search.

2. Navigation elements need to be easily discoverable

In addition to mimicking the basic website paradigm, the navigation elements in your app need to be easily discoverable. Despite the fact that some of the applications we tested had Back or Home buttons, some participants were not able to find them.

In the USA Today app, none of the participants realized that they needed to tap the USA Today logo to navigate to different news sections. Building a great app with rich content needs to be accompanied by a sound navigational structure that allows users to access the breadth and depth of your app without getting confused or frustrated.

Users failed to discover that tapping the USA Today logo would reveal navigation by section.

Other applications that we tested – like ESPN’s Score Center XL, Epicurious, and Wikipanion – had navigation elements that were only obvious when the iPad was in landscape mode. Participants that were already in landscape mode noticed these elements, but those that were using the iPad in portrait mode did not discover that they could turn the iPad 90° to uncover these features.

In landscape mode within the Epicurious Recipes & Shopping List app, users would have been able to sort by recipe categories and favorite recipes.

To ensure that your users discover all of your navigation elements – and don’t get lost in your app – make the most basic elements obvious and provide visual cues for elements that are more advanced or hidden.

3. Swipes are more fun than clicks

The touchscreen tablet platform opens the door to novel ways of interacting with content. Leverage touch gestures like swipes and flicks where appropriate, and where users most expect them. For example, users expect to be able to pinch or spread to zoom content – a convention learned from touchscreen mobile phones – and most participants in our testing understood and were delighted by the action of swiping to the next page in apps like the New York Times Editor’s Choice or Time Magazine.

Apple’s iBook application lets users swipe to turn the page in iBooks.

Again, ensure these sometimes unexpected ways of interacting with your content are discoverable by providing indications or visual cues to your users.

4. Keep an eye out for emerging standards

The iPad has only been available for a few months, so the platform is new and rapidly evolving. As more users adopt the iPad or other touchscreen tablet devices, standards for navigation and interaction will emerge that have yet to be established. Users will become more familiar with these standard interactions over time, but certain functionality may take a while to catch on or, certainly, to become ubiquitous.

In the meantime, make sure your app is simple to use. If you are pushing the envelope to institute your own set of standards, make sure they are discoverable and intuitive. Most importantly, test them amongst your users. Keep an eye out as standards emerge and be prepared to incorporate new best practices as they are defined.

Our latest report will help content owners and digital marketers create a winning digital content strategy across mobile platforms. Go here for more information about the iPad user experience research.

Early Days of Optimizing for the iPad

Friday, May 28th, 2010

Suzuki recently celebrated 50 years of international racing. As part of the celebration, they designed a new website optimized for the iPad.

http://www.suzuki50years.com/

At AnswerLab, we’ve heard from a number of our clients that they’d like to understand users’ expectations across platforms to help inform their design strategy. Should we design mobile apps or mobile optimized websites? Which mobile platform should we design for? What do users expect when they interact with our content on the iPad?

We conduct a ton of mobile user experience research at AnswerLab and now that the iPad has entered the picture, interest is gaining momentum. When I read about Suzuki’s latest creation, I immediately grabbed the AnswerLab shared iPad and brought up the site.

My first impression… It looks fantastic on the iPad.

Suzuki iPad Website

The designers obviously put energy into creating a site that fits well on the iPad’s screen. And Suzuki fully embraced the iPad/iPhone touch interface, allowing one to traverse the site via a simple swipe to change pages. As an iPhone owner, I’m used to performing this action in iPhone apps and the extension of this gesture to the web page is gratifying — albeit a bit unfamiliar.

While writing this blog post, I discovered Apple’s list of iPad ready websites and I’m sure there are others. I intend to check many of them out to see how well they’ve embraced the iPad’s unique format.

Whenever there is an iPhone optimized website, I’ll opt for it when browsing on my iPhone. Given that the iPad’s screen is much larger than my iPhone, only time will tell if I will prefer an iPad optimized website or the standard version of a website.

As your company decides which platform to embrace and whether to create an app or a mobile optimized site, consider your target audience and especially what experience you are bringing to the table. Suzuki may not have a huge iPad audience at this time but by creating an iPad optimized site, they are taking a risk and learning what works, and what doesn’t. At AnswerLab, we conduct research for industry-leaders to minimize their risk. When the platform is new and your audience is relatively small, risks like the one Suzuki is taking with this site may be somewhat trivial. However, prototype testing, conducting research, and fully understanding your users needs becomes paramount as the platform matures and users’ expectations become clear.

Recently, AnswerLab conducted testing to understand mobile consumers’ behaviors when purchasing apps and interacting with mobile devices including the iPad. Look for more information based on our findings in the near future.