Android code smells: From introduction to refactoring

Object-oriented code smells are well-known concepts in software engineering that refer to bad design and development practices commonly observed in software systems. With the emergence of mobile apps, new classes of code smells have been identified by the research community as mobile-specific code smells. These code smells are presented as symptoms of important performance issues or bottlenecks. Despite the multiple empirical studies about these new code smells, their diffuseness and evolution along change histories remains unclear. We present in this article a large-scale empirical study that inspects the introduction, evolution, and removal of Android code smells. This study relies on data extracted from 324 apps, a manual analysis of 561 smell-removing commits, and discussions with 25 Android developers. Our findings reveal that the high diffuseness of mobile-specific code smells is not a result of releasing pressure. We also found that the removal of these code smells is generally a side effect of maintenance activities as developers do not refactor smell instances even when they are aware of them. (C) 2021 Elsevier Inc. All rights reserved.

Automated summary

Object-oriented code smells refer to bad design and development practices seen in software systems. The emergence of mobile apps has brought about new mobile-specific code smells, which are symptoms of important performance issues. However, the removal of these code smells often occurs as a side effect of maintenance activities, with developers not always refactoring them even when aware of their presence.