Mobile development trade-offs vary by platform task and quality
Cross-Platform vs Native Mobile Development: An Empirical Study of Software Quality Trade-offs
Software EngineeringComputer Science and Game TheoryPerformance
Summary
Choosing how to build mobile apps is tricky because different approaches have different strengths and weaknesses. The authors studied five ways to create the same app on both iPhone and Android, comparing speed, size, and responsiveness. Native apps were fastest overall, but some cross-platform methods came close in certain tasks. The best choice depends on what matters most for the app and which platform it targets.
What this means in practice
- •For mobile app developers: Decide which mobile development framework best fits specific app tasks by comparing real-world quality and performance trade-offs across iOS and Android.
- •For software project managers: Plan project timelines and resource allocation by understanding effort and quality differences between native and various cross-platform mobile development approaches.
Authors
Alexandru Ilovan
Abstract
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.