An Empirical Evaluation of the User Interface Energy Consumption of React Native and Flutter

Bachelor Thesis (2019)
Author(s)

E.W. Blokland (TU Delft - Electrical Engineering, Mathematics and Computer Science)

Contributor(s)

Faculty
Electrical Engineering, Mathematics and Computer Science
Copyright
© 2019 Erik Blokland
More Info
expand_more
Publication Year
2019
Language
English
Copyright
© 2019 Erik Blokland
Graduation Date
28-06-2019
Awarding Institution
Delft University of Technology
Project
['CSE3000 Research Project']
Programme
['Computer Science and Engineering']
Faculty
Electrical Engineering, Mathematics and Computer Science
Reuse Rights

Other than for strictly personal use, it is not permitted to download, forward or distribute the text or part of it, without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license such as Creative Commons.

Abstract

Energy efficiency is a growing area of concern for mobile developers, as good battery life is highly desired by end users of mobile devices. While many developers work to increase their app's energy efficiency during development, there is not much information available about the energy efficiency of the different app frameworks on the market. As the choice of a framework must be made before the start of development, and cannot be easily changed later on, information about these frameworks is crucial to allow developers to optimize their apps for efficiency.
In this paper, we compare the energy use of the React Native and Flutter frameworks while performing User Interface tasks to the native Android API. While we were unable to draw a conclusion about whether one of these frameworks is more or less efficient than the baseline app, we were able to identify certain UI actions that were consistently more or power-hungry than average, and found that the energy use tendencies of these actions tended to be consistent between different frameworks and devices. We also found that measuring overall energy use between separate test runs was inconsistent, and further research may be necessary to identify the best method to isolate the energy use of a single app.

Files

License info not available