Volume 28, Issue 1 e1654
RESEARCH ARTICLE

Why does the orientation change mess up my Android application? From GUI failures to code faults

Domenico Amalfitano

Department of Electrical Engineering and Information Technologies, University of Naples Federico II, Via Claudio 21, Naples, Italy

Search for more papers by this author
Vincenzo Riccio

Department of Electrical Engineering and Information Technologies, University of Naples Federico II, Via Claudio 21, Naples, Italy

Search for more papers by this author
Ana C. R. Paiva

Faculty of Engineering of the University of Porto, Porto, Portugal

Search for more papers by this author
Anna Rita Fasolino

Corresponding Author

Department of Electrical Engineering and Information Technologies, University of Naples Federico II, Via Claudio 21, Naples, Italy

Correspondence

Anna Rita Fasolino, Department of Electrical Engineering and Information Technologies, University of Naples Federico II, Via Claudio 21, Naples, Italy.

Email: anna.fasolino@unina.it

Search for more papers by this author
First published: 06 November 2017
Citations: 11

Summary

This paper investigates the failures exposed in mobile apps by the mobile‐specific event of changing the screen orientation. We focus on GUI failures resulting in unexpected GUI states that should be avoided to improve the apps quality and to ensure better user experience. We propose a classification framework that distinguishes 3 main classes of GUI failures due to orientation changes and exploit it in 2 studies that investigate the impact of such failures in Android apps. The studies involved both open‐source and apps from Google Play that were specifically tested exposing them to orientation change events. The results showed that more than 88% of these apps were affected by GUI failures, some classes of GUI failures were more common than others, and some GUI objects were more frequently involved. The app source code analysis allowed us to identify 6 classes of common faults causing specific GUI failures.

The full text of this article hosted at iucr.org is unavailable due to technical difficulties.