Cross-Platform vs Native Mobile Development: An Empirical Study of Software Quality Trade-offs
原文链接: https://arxiv.org/abs/2609.21544
作者: Alexandru Ilovan
发布时间: 2026-09-18
源: arxiv
摘要
arXiv 2609.21544 对同一应用做了五种实现:native iOS、native Android、Flutter、React Native、KMP;共享跨平台实现同时打 Android 与 iOS,共八个可执行变体。指引是 ISO/IEC 25010,考察时间行为、实现足迹、源代码组织、可观察的渲染响应;同一应用域、后端服务、功能需求与 benchmark 契约,数据集含每变体 2000 次完整 run。原生客户端耗时最低,KMP 是最接近的跨平台实现;任务不同排名会翻转——结论是「看任务」,但数据集干净可当引用素材。
English Summary
arXiv 2609.21544 builds five implementations of the same plant-management application — native iOS, native Android, Flutter, React Native, and Kotlin Multiplatform — and the shared cross-platform implementations target both Android and iOS, yielding eight executable variants. Guided by ISO/IEC 25010, the study covers time behavior, implementation footprint, source-code organization, and observable rendering responsiveness under a shared domain, backend, functional spec, and benchmark contract; the dataset contains 2,000 completed runs per variant. Native clients are fastest in wall-clock cost, KMP is the closest cross-platform implementation, and the ranking flips on different tasks. The headline message is 'it depends on the task,' but the clean dataset makes the paper useful as a reference.
为什么值得关注
主题线扩展 AAIF cross-platform/flutter/react-native/kmp 等主题。