Clone-Based Variability Management in the Android Ecosystem
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
Mobile app developers often need to create variants to account for different customer segments, payment models or functionalities. A common strategy is to clone (or fork) an existing app and then adapt it to new requirements. This form of reuse has been enhanced with the advent of social-coding platforms such as Github, cultivating a more systematic reuse. Different facilities, such as forks, pull requests, and cross-project traceability support clone-based development. Unfortunately, even though, many apps are known to be maintained in many variants, little is known about how practitioners manage variants of mobile apps. We present a study that explores clone-based reuse practices for open-source Android apps. We identified and analyzed families of apps that are maintained together and that exist both on the official app store (Google Play) as well as on Github, allowing us to analyze reuse practices in depth. We mined both repositories to identify app families and to study their characteristics, including their variabilities as well as code-propagation practices and maintainer relationships. We found that, indeed, app families exist and that forked app variants fall into the following categories: (i) re-branding and simple customizations, (ii) feature extension, (iii) supporting of the mainline app, and (iv) implementation of different, but related features. Other notable characteristic of the app families we discovered include: (i) 72.7% of the app families did not perform any form of code propagation, and (ii) 74% of the app families we studied do not have common maintainers.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Social coding in GitHub: transparency and collaboration in an open software repository
Dabbish, L., Stuart, C., Tsay, J., & Herbsleb, J. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145396 · Cited by 999
Curating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365 · cited 1×
“of finding student assignments, which could pollute our results [10].”
Research works printed but not linked: 13
- 10.1145/2597073.2597074 · DOI · Paper page
- 10.1145/3127005.3127009 · DOI
- schmid, 0, Domain-oriented customization of service platforms: Combining product line engineering and service-oriented computing, Journal of Universal Computer Science, 19, 233
- 10.1145/2648511.2648514 · DOI
- werber, 2015, Uncovering variability models for software ecosystems from multi-repository structures, VAMOS, 10.1145/2701319.2701333 · doi:10.1145/2701319.2701333
- 10.1145/2791060.2791108 · DOI
- 10.1016/j.infsof.2014.05.005 · DOI
- 10.1007/978-3-642-37521-7 · DOI · Paper page
- krüger, 2018, Towards a better understanding of software features and their characteristics: A case study of marlin, VAMOS
- 10.1109/MS.2013.142 · DOI · Paper page
- 10.1109/CSMR.2013.13 · DOI · Paper page
- 10.1145/2934466.2946047 · doi:10.1145/2934466.2946047
- 10.1007/s10515-017-0228-z · DOI
Cited by
Causes of merge conflicts: a case study of ElasticSearch
Mahmood, W., Chagama, M., Berger, T., & Hebig, R. (2020) · Proceedings of the 14th International Working Conference on Variability Modelling of Software-Intensive Systems · doi:10.1145/3377024.3377047 · Cited by 10
Self-citationPaReco: patched clones and missed patches among the divergent variants of a software family
Ramkisoen, P. K., Businge, J., van Bladel, B., Decan, A., Demeyer, S., De Roover, C., & Khomh, F. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3549112 · Cited by 10
Self-citationVariant Forks - Motivations and Impediments
Businge, J., Zerouali, A., Decan, A., Mens, T., Demeyer, S., & De Roover, C. (2022) · 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00105 · Cited by 7
“This process is subject to a known threat to validity since previous studies revealed that the majority of forks on GitHub are inactive [24], [25] or are social forks [21].”
BackgroundResultSelf-citationAnalyzing Variant Forks of Software Repositories from Social Coding Platforms
Businge, J., Abdi, M., & Demeyer, S. (2023) · Software Ecosystems · doi:10.1007/978-3-031-36060-2_6 · Cited by 1
Self-citationAgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub
Ogenrwot, D., & Businge, J. (2026) · Proceedings of the 3rd ACM International Conference on AI-Powered Software · doi:10.1145/3805760.3814923
“Certain merge simulation failures may arise when repositories have been deleted or historical commits are no longer reachable due to force-pushes or history rewrites [5, 9, 45].”
Self-citation
Metadata
- Authors
- Businge, J., Openja, M., Nadi, S., Bainomugisha, E., & Berger, T.
- Venue
- 2018 IEEE International Conference on Software Maintenance and Evolution (ICSME)
- Publisher
- IEEE
- Published
- 2018-09
- Pages
- 625-634
- OpenAlex
- W2900472033
- Cited by
- 38
- References
- 2
- FWCI
- 4.98
- 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
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.