An empirical analysis of energy consumption of cross-platform frameworks for mobile development

Ciman, Matteo; Gaggi, Ombretta

doi:10.1016/j.pmcj.2016.10.004

Cited by 53 publications

(40 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[8]). Hardware-near, high performance apps require native development [40]. Rather simple, form-based apps are quickly developed as Webapps [15], [29].…”

Section: Baseline: Native Development and Webappsmentioning

confidence: 99%

“…[40]). This is true not only regarding cross-platform development frameworks but also for any other development technology, even if it is not specific to multi-platform development.…”

Section: Baseline: Native Development and Webappsmentioning

confidence: 99%

“…Their research includes measuring energy consumption using different devices and scenarios. For further research, we propose drawing from the results of both [21] and Ciman and Gaggi' research [40] on energy consumption of crossplatform app development frameworks and approaches.…”

Section: Literature Coveragementioning

confidence: 99%

See 2 more Smart Citations

Progressive Web Apps: the Definite Approach to Cross-Platform Development?

Majchrzak¹,

Biørn-Hansen²,

Grønli³

2018

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Although development practices for apps have matured, cross-platform development remains a prominent topic. Typically, apps should always support both Android and iOS devices. They ought to run smoothly on various hardware, and be compatible with a host of platform versions. Additionally, device categories beyond smartphone and tablets have emerged, which makes multi-platform support even trickier. Truly developing an app once and serving the multitude of possible targets remains an issue despite having crossplatform frameworks that are acknowledged by practice and research. The technology unifier remains to be found, but Progressive Web Apps (PWA) might be a step towards it. In this paper, we analyse the foundations of PWAs in cross-platform development and scrutinize the status quo of current possibilities. Based on our observations, we investigate unified development, and discuss open questions. We seek to stimulate interest and narrow the immense gap that has arisen since industry started to embrace PWAs.

show abstract

“…[8]). Hardware-near, high performance apps require native development [40]. Rather simple, form-based apps are quickly developed as Webapps [15], [29].…”

Section: Baseline: Native Development and Webappsmentioning

confidence: 99%

“…[40]). This is true not only regarding cross-platform development frameworks but also for any other development technology, even if it is not specific to multi-platform development.…”

Section: Baseline: Native Development and Webappsmentioning

confidence: 99%

See 1 more Smart Citation

Progressive Web Apps: the Definite Approach to Cross-Platform Development?

Majchrzak¹,

Biørn-Hansen²,

Grønli³

2018

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

show abstract

“…However, implementations are used also for studies such as comprehensive performance tests (e.g. [14]) and comparison of development approaches (e.g. [13]).…”

Section: Related Workmentioning

confidence: 99%

“…These frameworks rely on their own implementation of bridges, as no standard has yet been defined. We will build on the method and data presented in Section 6, and design a comprehensive study targeting performance differences between such frameworks, drawing from previous performance-oriented research such as [14]. Additionally, we will further investigate other topics arising from the upcoming survey questionnaire study mentioned.…”

Section: Page 5723mentioning

confidence: 99%

Bridging the Gap: Investigating Device-Feature Exposure in Cross-Platform Development

Biørn-Hansen

Ghinea

2018

Proceedings of the 51st Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

By traversing academia and developer communities, two predominant approaches to cross-platform mobile development have been identified, specifically Hybrid and Interpreted. Previous research has established the use and integration of platform-and device-specific features to be core requirements for cross-platform frameworks. In this study we assess and discuss how the Hybrid and Interpreted approaches facilitate the use of native device features from within a JavaScript context, and how custom communication bridges are both developed and integrated. Our research motivation lies in data from an industry survey, stating that developers perceive device communication as a real painpoint. While both approaches exist to ease development of mobile apps, they are fundamentally different at a technical level. The article takes a technical approach, drawing evaluations and discussions from two app implementations. Our findings indicate that implementation and development of communication bridges are non-complex tasks, and that execution-time performance varies greatly.

show abstract