Blog

Why app design defects should not be “won’t fix”. Part 2

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?
30 September 2014
Quality assurance
The article by a1qa
a1qa

We continue the topic of design defects. In case you missed the first part of the article, you can read it here.

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:

  • 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.

The article Why app design defects should not be “won’t fix” was published in Mobile Marketer online edition.

More Posts

Agile and DevOps in eCommerce QA_mini
30 September 2021,
by a1qa
5 min read
Agile and DevOps: Boosting the quality of eCommerce apps
What benefits do Agile and DevOps bring to eCommerce business, and how QA helps with that? Find it out in the article.
Agile
Quality assurance
AR/VR testing infographics mini
30 August 2021,
by a1qa
< 1 min read
AR/VR testing in retail: turning challenges into opportunities
Welcome to read the infographic on AR/VR in retail: new shopping experiences, issues, and how to address them with QA.
Quality assurance
6 October 2020,
by Dmitry Tishchenko
4 min read
A clear view of smart team scalability
Get to know how to scale your team sagely and gratify end-user needs and fast-paced tech-market requirements.
Agile
Quality assurance
6 August 2020,
by Elena Yakimova
5 min read
How to arrange fruitful joint work with an outsourcing QA team
The head of the web apps testing department sheds light on how to establish more transparent and effective work on the project cooperating with a remote QA team.
Quality assurance
4 June 2020,
by Vitaly Prus
4 min read
SAFe vs. Scrum, and PI planning essentials
Let's shed some light on the SAFe differences from Scrum that are to be considered by the development and QA teams who have migrated from Scrum.
Agile
Quality assurance
29 April 2020,
by a1qa
4 min read
5 lessons we learned from COVID-19
Here are five key lessons the businesses need to learn during this pandemic to somehow achieve the planned outcomes. 
Quality assurance
17 April 2020,
by a1qa
5 min read
QA-focused retrospective: identifying and solving project problems
The a1qa experts came up to consider an effective approach to identify project bottlenecks and get rid of problems successfully.
Agile
Quality assurance
31 March 2020,
by Dmitry Tishchenko
4 min read
QA outsourcing – the respond to unprecedented global challenge
How can companies meet their business-critical needs without health risks? QA outsourcing is the answer. Get to know why it is the right decision in this time of need.
QA consulting
Quality assurance
10 March 2020,
by a1qa
6 min read
Dedicated team model in QA: all you should know about it
Check on everything you should know about when to apply, how to run and pay for a dedicated team in QA.
Interviews
QA consulting
Quality assurance

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.