The DOI matches its Crossref record; 18 of the 18 references it cites were found in a registry or an index.
An Empirical Study of API Stability and Adoption in the Android Ecosystem
Abstract
When APIs evolve, clients make corresponding changes to their applications to utilize new or updated APIs. Despite the benefits of new or updated APIs, developers are often slow to adopt the new APIs. As a first step toward understanding the impact of API evolution on software ecosystems, we conduct an in-depth case study of the co-evolution behavior of Android API and dependent applications using the version history data found in github. Our study confirms that Android is evolving fast at a rate of 115 API updates per month on average. Client adoption, however, is not catching up with the pace of API evolution. About 28% of API references in client applications are outdated with a median lagging time of 16 months. 22% of outdated API usages eventually upgrade to use newer API versions, but the propagation time is about 14 months, much slower than the average API release interval (3 months). Fast evolving APIs are used more by clients than slow evolving APIs but the average time taken to adopt new versions is longer for fast evolving APIs. Further, API usage adaptation code is more defect prone than the one without API usage adaptation. This may indicate that developers avoid API instability.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Significance Testing of the Spearman Rank Correlation Coefficient
Zar, J. H. (1972) · Journal of the American Statistical Association · doi:10.1080/01621459.1972.10481251 · Cited by 689
Identifying reasons for software changes using historic databases
Mockus, & Votta (2000) · Proceedings 2000 International Conference on Software Maintenance · doi:10.1109/icsm.2000.883028 · Cited by 472
Significance Testing of the Spearman Rank Correlation Coefficient
Zar, J. H. (1972) · Journal of the American Statistical Association · doi:10.2307/2284441 · Cited by 396
CatchUp!: capturing and replaying refactorings to support API evolution
Henkel, J., & Diwan, A. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062512 · Cited by 269
Bootstrapping energy debugging on smartphones: a first look at energy bugs in mobile devices
Pathak, A., Hu, Y. C., & Zhang, M. (2011) · Proceedings of the 10th ACM Workshop on Hot Topics in Networks · doi:10.1145/2070562.2070567 · Cited by 198
Automated Static Code Analysis for Classifying Android Applications Using Machine Learning
Shabtai, A., Fledel, Y., & Elovici, Y. (2010) · 2010 International Conference on Computational Intelligence and Security · doi:10.1109/cis.2010.77 · Cited by 167
The role of refactorings in API evolution
Dig, D., & Johnson, R. E. (2005) · Proceedings/Proceedings - Conference on Software Maintenance · doi:10.1109/icsm.2005.90 · Cited by 157
How do developers react to API deprecation?
Robbes, R., Lungu, M. F., & Röthlisberger, D. (2012) · doi:10.1145/2393596.2393662 · Cited by 152
An empirical investigation into the role of API-level refactorings during software evolution
Kim, M., Cai, D., & Kim, S. (2011) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1985793.1985815 · Cited by 140
Self-citationAutomatic Inference of Structural Changes for Matching across Program Versions
Kim, M., Notkin, D. S., & Grossman, D. (2007) · Proceedings/Proceedings - International Conference on Software Engineering · doi:10.1109/icse.2007.20 · Cited by 135
Self-citation
Cited by
A Survey of App Store Analysis for Software Engineering
Martin, W., Sarro, F., Jia, Y., Zhang, Y., & Harman, M. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2630689 · Cited by 459
Kula, R. G., German, D. M., Ouni, A., Ishio, T., & Inoue, K. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9521-5 · Cited by 351
How do API changes trigger stack overflow discussions? a study on the Android SDK
Linares-Vásquez, M., Bavota, G., Di Penta, M., Oliveto, R., & Poshyvanyk, D. (2014) · Proceedings of the 22nd International Conference on Program Comprehension · doi:10.1145/2597008.2597155 · Cited by 146
Automated reporting of GUI design violations for mobile apps
Moran, K., Li, B., Bernal-Cárdenas, C., Jelf, D., & Poshyvanyk, D. (2018) · Proceedings of the 40th International Conference on Software Engineering · doi:10.1145/3180155.3180246 · Cited by 101
Metadata
- Authors
- McDonnell, T., Ray, B., & Kim, M.
- Venue
- 2013 IEEE International Conference on Software Maintenance
- Publisher
- IEEE
- Published
- 2013-09
- Pages
- 70-79
- ISSN
- 1063-6773 (ISSN-L)
- OpenAlex
- W2022429945
- Cited by
- 304
- References
- 18
- FWCI
- 17.22
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: An Empirical Study of API Stability and Adoption in the Android Ecosystem. https://app.cochat.ai/papers/10.1109/icsm.2013.18
- The paper
- McDonnell, T., Ray, B., & Kim, M. (2013). An Empirical Study of API Stability and Adoption in the Android Ecosystem. 2013 IEEE International Conference on Software Maintenance. https://doi.org/10.1109/icsm.2013.18
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.