2019 24th International Conference on Engineering of Complex Computer Systems (ICECCS) 2019
DOI: 10.1109/iceccs.2019.00029
|View full text |Cite
|
Sign up to set email alerts
|

On the Evolution of Mobile App Complexity

Abstract: Android developers are known to frequently update their apps for fixing bugs and addressing vulnerabilities, but more commonly for introducing new features. This process leads a trail in the ecosystem with multiple successive app versions which record historical evolutions of a variety of apps. While the literature includes various works related to such evolutions, little attention has been paid to the research question on how quality evolves, in particular with regards to maintainability and code complexity. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
5
4

Relationship

2
7

Authors

Journals

citations
Cited by 14 publications
(4 citation statements)
references
References 31 publications
0
4
0
Order By: Relevance
“…Considering, that this information is not always present in submitted bug reports (missing in 30% of the cases), techniques that are able to infer, prioritize environmental settings (e.g., device and platform versions) are needed to help drive research on more advanced automated mobile bug report analysis techniques. Furthermore, considering that apps are released frequently [44], [45] and bug reports do not always contain the associated app version, it would be beneficial to automatically infer the version of the app associated with a bug report. This task could be done by automatically by mapping bug report information into GUI components or code entities in the app.…”
Section: Rq 4 : Do Discussion Threads Of Reproducible Bug Reports Con...mentioning
confidence: 99%
“…Considering, that this information is not always present in submitted bug reports (missing in 30% of the cases), techniques that are able to infer, prioritize environmental settings (e.g., device and platform versions) are needed to help drive research on more advanced automated mobile bug report analysis techniques. Furthermore, considering that apps are released frequently [44], [45] and bug reports do not always contain the associated app version, it would be beneficial to automatically infer the version of the app associated with a bug report. This task could be done by automatically by mapping bug report information into GUI components or code entities in the app.…”
Section: Rq 4 : Do Discussion Threads Of Reproducible Bug Reports Con...mentioning
confidence: 99%
“…First, we use 42 source code metrics that have been defined and used in previous experiments related, for instance, to the assessment of the overall quality of the software [15], [16], [17], [18], [19], [20], [21], [22]. These metrics are grouped in different categories like inheritance, communication, and complexity and readability.…”
Section: B Instantiating Migrationexp For Supporting Java To Kotlin M...mentioning
confidence: 99%
“…App complexity is an elusive concept. Yet, in the literature, there are various studies that propose metrics to measure some form of complexity and attempt to show its correlation with app quality and maintainability (Jošt et al 2013;Gao et al 2019b). We undertake to investigate our research question based on these common metrics from the literature (Chidamber and Kemerer 1994).…”
Section: Do Covid-related Apps Have Specific Characteristics?mentioning
confidence: 99%