Testing mobile apps isn & # x27; t always easy. Testing the nomadic user experience can be particularly difficult. But like well-nigh every other pursuit in life, it ’ s possible to achieve with the right attack and measure of effort.

In this post, we & # x27; ll appear at some of the major hard-to-test mobile user experience challenges, and how you can address them in testing your mobile app.

The Big Crash

Nobody require his or her app to crash. It ’ s not just frustrating for users and developer alike, but it ’ s also costly to the business.

In the mobile macrocosm, the cost of a crash can be lots higher than it is for a desktop app. Unless you & # x27; re lucky enough to be the developer of an absolutely indispensable app with a locked-in user base, chances are very good that if your app clangoring, most users will only stop use it (or just uninstall it) in favor of a competing (and non-crashing) app.

The weather that cause a crash, unluckily, are not always easy to predict. Even if your app behaves well internally, it may crash in response to trouble with accession to operating system or hardware resource, or early external conditions. It doesn & # x27; t even matter whether your app is the one induce the canonical problem, as long as it & # x27; s the one that crashes.

The best way to test for crashes and former ruinous failure is generally by means of a large-scale machine-controlled try platform with a broad orbit of device. This will allow you to try under the all-embracing variety of weather, and anticipate the great majority of potential crash scenarios.

Speed, and the Lack of It

Users don & # x27; t like slow apps—In fact, they & # x27; re almost as potential to uninstall a dull app as they are one that crashes. As with crashes, you can & # x27; t ever foresee the conditions that will decelerate your app down, and those weather may depend on circumstances that you can & # x27; t control.

Slowdowns, however, may result from problems in access datum, sooner than scheme resources. When you & # x27; re waiting for content, you may not be capable to operate how chop-chop (or whether) it will arrive, but you can operate the way that your app wad with slow or non-arriving content.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

This imply that in improver to the kind of large-scale automated tryout that you would use to look for crashes, you need to test your app & # x27; s behavior when content get tardily or is unavailable. It should always appear to the user that the app is doing something (loading the framework of a page, etc.), and the app should perpetually display a simple, informatory duologue box in the instance of a timeout.

Don & # x27; t Drain the Battery!

Your app shouldn & # x27; t draw any more power than it needs to. Chances are that you & # x27; ve contrive it to be at least reasonably good at not drain the battery under ordinary circumstance. But what happens when the user or the system does something that you hadn & # x27; t forestall? Are there circumstances, for representative, where a process which should only run for a little time will continue to run in the background? Are there times when your app may download unnecessary information, or maintain high-demand scheme resources when it doesn & # x27; t need to?

The same kinds of large-scale automated tests that can be habituate for crashes and slowdown are also full for detecting conditions that may drain the battery. Be sure to include power consumption issues in your examination results analytics.

Design Disasters

The majority of user experience job are the solvent of bad (or at least not well thought-out) design. Unfortunately, these are much the problem that are the hardest to detect. They don & # x27; t ram the app, and they don & # x27; t make any obvious functional problems. They merely make what should be simple actions unmanageable, annoy user, and create it more likely that they will switch to a competing app. For the most part, design job fall into a few introductory areas:

Navigation and Flow

Users take to be able to navigate through your app easily. It should use standard piloting conventions whenever possible. If you require to provide a alone navigation method, it should not conflict with existent measure.

Flow of use is as important as navigation. Flow depends on the main intention of your app. How quickly and how well can user get to key functions? They shouldn & # x27; t have to take an indirect route or back out of one use to get to another (unless it & # x27; s absolutely necessary).

Don & # x27; t Stop the User

Full flowing also means that you shouldn & # x27; t stop users and ask them for things such as authorization when you don & # x27; t require to. (The clip to ask them is when you know that you & # x27; ll need the authorization, not simply when they start the app, or when they conduct an action which may or may not eventually expect authorization.)

Clutter and Confusion

Each screen should be clear, and whenever possible, focused on a single purpose. Functional elements should be visually distinguishable from purely decorative elements. Screens should not present the user with more functions, information, or decision than necessary, and users shouldn & # x27; t receive to decipher one screen to get to the next one (unless it & # x27; s a game, and you & # x27; re giving them puzzles).

No Bad Buttons

Buttons should be of enough sizing, with sufficient distance between them so that the user is improbable to accidentally press the wrong button. If you need to crowd too many button onto one screen, it & # x27; s plausibly a mark that you should reorganise the layout of your app.

Text Trouble

Text needs to be of decent size and line, and in an easily clear font. Text input on most mobile device isn & # x27; t that easy for many users, so you should require them to enter as slight text as potential, or avoid text comment altogether.

Testing Design Issues

How do you test for plan problems such as these? Ultimately, you will need to test with a direction group of hands-on users who can give you honest and informed feedback. By recording their activeness and listening to what they have to say, you can fine-tune your design for optimum flow and ease of use.

You can, however, use automatize testing to pick up a considerable number of design problem betimes on by logging such things as the time required to perform canonic undertaking and betray effort to perform such tasks, as well as examining screen recordings of automated user interface tryout. A well planned-out automated testing regime may allow you to detect even many very subtle user interface problems before you go on to (generally more costly and time-consuming) live exploiter tests.

Michael Churchman commence as a scriptwriter, editor, and producer during the anything-goes early days of the game industry. He spent much of the 90s in the high-pressure bundled software diligence, where the motion from waterfall to faster liberation was well under way, and near-continuous release cycle and automated deployment be already de facto standards. During that time he germinate a semi-automated scheme for managing localization in over xv lyric. For the preceding ten years, he has be involved in the analysis of software development processes and related technology management issue. He is a veritable Fixate.io contributor ..