By Tatyana Mahlaeva

Are you sure that users will love the application that you are going to produce? After all, this is the key for commercial success. Unfortunately, sometimes, even great ideas fail due to bad implementation. How do you prevent this from happening?

The answer is proper testing before the product hits the market. At the same time, however, when it comes to usability and design issues detected by a tester, it is quite common to hear things such as, “Not too serious,” “No time to fix” or “Too expensive!”

It is important to avoid the “won’t fix” reaction from the development team in the event that the tester finds a significant defect. Below are some tips to help ensure applications’ quality and that all defects found will be fixed.

Views on use
First of all, let us talk about usability of a mobile application. No, we will not touch the usability testing in its full and heavy sense – with a lot of users for evaluation and scrupulous analysis of the target audience.

Rather, I mean the base layer of usability checks – the layer that the functional tester is able to perform himself or herself without investing a huge amount of time and money.

The key things are, of course, clear logic and simplicity. This applies to all kinds of applications – games, office suites, enterprise software, everything.

Is the application intuitive enough to use it easily right after the installation? If no, does the application have clear help, FAQs, tips, other useful FTU (first-time user) resources? Are these resources easily accessible?

These are the questions that the tester should answer while implementing usability tests.

If we consider games, it is important to examine the power balance and energy saving system.

For any type of mobile organizer, it is essential to find out if users are able to see the most important events and functions at the starting screen. They will also want a quick and easy way to add a new note to the organizer.

Listed issues are based mostly on the functionality of the application. In fixing them, you could help to keep users from abandoning the application – considering it illogical or useless.

Also important and connected to usability is an application’s graphics – how the design corresponds to the application’s purpose.

Would you find it appropriate to use all the colors of the rainbow for highly secure government applications? Certainly not. This is unnecessary and would look ridiculous.

That is why it is so important to use testing methods while evaluating application design. In doing so, you will most likely need several devices with different specs.

Texts and objects used in the applications should be noticeable enough and stand out against the background color.

If the font is difficult to read, this may lead to increased user’s annoyance.

You also need to get a negative response to the following questions to ensure that the application is good in terms of design.

For example, is the text too small for the 5-inch device screen? Are there too many targets or icons on the screen? Does the application respond correctly to standard gestures – for instance, “pinch in” is commonly used by mobile devices for zoom-out?

Graphic description
There is another group of graphic defects connected not to usability, but mostly the application functionality itself.

Among them: FPS rate (frames per second). Is it good enough for high-performance games? Does the application display properly both in portrait and landscape orientations on the screen?

This group of possible defects is a must-know for any mobile QA engineer since they are official mobile development compliances.

The most useful and known among them are iOS Human Interface Guidelines (iOS HIG) and Android User Interface Guidelines (Android UIG).

These documents could help provide serious arguments in discussions with developers about potential “won’t fixes.”

Recommendations presented in these docs are not strict rules, especially for Android, but they are really useful in terms of user interaction and pretty stable for a long time with minor changes, which is a good sign that they are truly functional.

Below you can find a selection of such recommendations concerning design and a small part of the whole list. For the full version please see the original documents, linked to above:

• The app should not contain depictions of gratuitous violence (iOS)
• The app should not contain materials advocating against groups of people based on their race, religion, disability, gender, age, etc. (iOS)
• The app should not contain sexually explicit or erotic content, icons, titles or descriptions (Android and iOS)
• Use illumination and dimming to respond to touches, reinforce the resulting behavior of gestures, and indicate what actions are enabled and disabled (Android)
• UI elements should have 8dp spacing (Android)
• Touchable UI components should be laid out along 48dp units (Android)
• Custom UI elements should not be used for a standard action (iOS)
• UI must be optimized both for Retina and non-Retina displays (iOS)
• UI elements from different versions of iOS should not be mixed (iOS)
• The app must not contain materials or services that facilitate online gambling (Android)

THESE ARE just a few examples of usability and graphics recommendations that are presented in the official documents for iOS and Android – easily accessible when needed to state your case with developers during “won’t fix” discussions.

If nothing else, remember this: even if the application is extremely good in terms of the idea, if fonts are too small to read, colors are too bright, backlighting of important areas is absent, and other usability challenges exist, users will not get past the exterior to experience the gem on the inside.

Tatyana Mahlaeva is mobile applications QA manager for A1QA, an Austin, TX-based global software testing and quality assurance company. Reach her at [email protected].