Metraipolis › archive › dc_998e10ee545f
Cross-Platform vs Native Mobile Development: An Empirical Study of Software Quality Trade-offs — arXiv:2609.21544
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.21544
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-10T01:40:22.942Z
- SHA-256 of the archived text
13eb3be049d749b488339b8f204f49acb925bbddab08ca8c26615b1b428b6b02- Stable URL of this page
https://metraipolis.com/documento/dc_998e10ee545f
How to cite
Cross-Platform vs Native Mobile Development: An Empirical Study of Software Quality Trade-offs — arXiv:2609.21544 — arXiv (en), https://arxiv.org/abs/2609.21544 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_998e10ee545f (Metraipolis archive dc_998e10ee545f, sha256 13eb3be049d749b488339b8f204f49acb925bbddab08ca8c26615b1b428b6b02)
BibTeX
@misc{dc998e10ee545f,
title = {Cross-Platform vs Native Mobile Development: An Empirical Study of Software Quality Trade-offs — arXiv:2609.21544},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.21544},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_998e10ee545f; sha256 13eb3be049d749b488339b8f204f49acb925bbddab08ca8c26615b1b428b6b02},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.21544. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Cross-platform mobile frameworks promise code reuse, shorter delivery cycles, and lower implementation effort, but their trade-offs relative to native development remain difficult to assess objectively. Many comparisons rely on simplified applications, inconsistent feature sets, or a narrow set of metrics. This paper compares five implementations of the same plant-management application: native iOS, native Android, Flutter, React Native, and Kotlin Multiplatform. The shared approaches target both Android and iOS, yielding eight executable variants. Guided by ISO/IEC 25010, the study examines time behavior, implementation footprint, source-code organization, and observable rendering responsiveness. All implementations share the same domain, backend services, functional requirements, and benchmark contract. The supplied dataset contains 2,000 completed runs per variant and covers authenticated and cached retrieval, image transfer and decoding, list rendering and scrolling, local synchronization, and media upload. Backend preparation and framework-specific UI drivers are analyzed separately from the primary client workflow. Native records the lowest non-UI client subtotal on both operating systems, with Kotlin Multiplatform the closest cross-platform implementation, while operation and UI-wrapper rankings vary by task. The shared approaches contain less authored mobile source than the native applications combined, and the source inventory shows different patterns of file size, organization, and dependency use. Rather than identifying a universally superior technology, the study shows that each approach's advantages and costs depend on the quality attribute, workload, platform, and measurement boundary. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-21 in cs.PF). Categorie arXiv: Software Engineering (cs.SE) ; Computer Science and Game Theory (cs.GT); Performance (cs.PF). Pagina del lavoro: https://arxiv.org/abs/2609.21544 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-10T01:08:03.190Z dalla pagina https://arxiv.org/catchup/cs.PF/2026-09-21?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).