It’s no secret that mobile user testing is just as important as testing your web app. In fact, it may be even more critical to your success, especially if you have a heavily reliant on mobile users. Think: Lyft or Instagram which are almost entirely on mobile.
Mobile is.. well, mobile! Your user is unlikely to be sitting as a desk in a chair. They could be on the bus, walking down the street, or even, yes, in the bathroom. Consideration about when, where and how a user navigates your mobile app can help set the right context. Your mobile app may be specific for location (think Google Maps, or a GPS athletic tracker such as Strava).
Consider: Have you thought about where your users may be, or you need them to be, for accurate results? If you’re testing in a lab, you may be OK with low-priority issues, however, you may miss the context for high-severity issues.
It’s all about context, and yes the possibility of a user sitting on the throne in the bathroom. Privacy is a greater concern when testing on mobile.
Consider: What kind of data are you ingesting? Are you capturing their location in addition to screencast and video? What implications might any of those have on your test? Might you see other data such as personal photographs as they navigate in between apps or other data on their phone that may otherwise be private?
Shorter interactions are likely. Not necessarily in duration, but regardless of how large that phablet is, it’s still not a laptop nor a desktop, so the content will need to be fitted appropriately.
Consider: What specific parts of your test have you designed that allow for shorter interactions.
Interruptions. Your users are likely to be interrupted. They might receive a text message, or some other app’s notification while they are undergoing your test. The text from their mother is probably far more important, so expect that your test might get put on hold.
Consider: Have you thought about how to structure your test so it’s easy to come back to?
- Non-linear flow. A mobile experience is not a single user experience as there are often many pathways a user takes to accomplish a task. Consider: Testing multiple pathways will help you develop an application that fits into your users life.