Leafactor: Improving Energy Efficiency of Android Apps via Automatic Refactoring

Cruz, Luís; Abreu, Rui; Rouvignac, Jean-Noel

doi:10.1109/mobilesoft.2017.21

Cited by 28 publications

(12 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, we still lack empirical study on the effect of fixing Android smells through refactoring, mainly concerning memory and CPU usage. Studies regarding automatic detection and analysis of the impact of the refactoring on the Android platform are still premature [5].…”

Section: Introductionmentioning

confidence: 99%

An Empirical Study on the Impact of Android Code Smells on Resource Usage

Oliveira¹,

Viggiato²,

Santos³

et al. 2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Code smells are symptoms that something may be wrong with the app. Aiming at removing code smells and improving the maintainability and performance of the app, we may apply the refactoring technique, which could reduce hardware resource use, such as CPU and memory. However, a few studies have evaluated the impacts of the refactoring in Android. This paper presents a study to assess the effects of smartphone resource use caused by refactoring of 3 classic code smells: God Class, God Method, and Feature Envy. To this purpose, we selected 9 apps from GitHub. The results show that refactoring used in desktop software may not be appropriate for Android apps. For example, the refactoring of God Method had increased CPU consumption by more than 47%, while the refactoring of the 3 code smells reduced memory consumption in average 6.51%, 8.4%, and 6.37%, respectively, in one app. Our results can support the community in conducting research and future implementation of new tools. Also, it guides app developers in refactoring and thus improving the quality of their apps.

show abstract

Section: Introductionmentioning

confidence: 99%

An Empirical Study on the Impact of Android Code Smells on Resource Usage

Oliveira¹,

Viggiato²,

Santos³

et al. 2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…The majority of these approaches address the application source code (38/85). Changes to source code included the removal of bad coding practices (antipatterns) [181], [182], [192], or refactoring to include best practices [190], [191], [194]. Source code adaptation approaches can also focus on particular elements of devices, such as the display.…”

Section: Discussionmentioning

confidence: 99%

“…Another approach to automatically refactor applications is to follow energy efficiency guidelines [190], [191], [194]. Cito et al [146] adapted application binaries to adjust the frequency of network requests to advertisements and analytics based on the battery status.…”

Section: Optimization Approachesmentioning

confidence: 99%

A Survey of Performance Optimization for Mobile Applications

Hort

Kechagia

Sarro

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

To ensure user satisfaction and success of mobile applications, it is important to provide highly performant applications. This is particularly important for resource-constrained systems such as mobile devices. Thereby, non-functional performance characteristics, such as energy and memory consumption, play an important role for user satisfaction. This paper provides a comprehensive survey of non-functional performance optimization for Android applications. We collected 156 unique publications, published between 2008 and 2020, that focus on the optimization of performance of mobile applications. We target our search at four performance characteristics: responsiveness, launch time, memory and energy consumption. For each performance characteristic, we categorize optimization approaches based on the method used in the corresponding publications. Furthermore, we identify research gaps in the literature for future work.

show abstract

“…In [19] the authors base their work on 5 built-in checks of Android lint that they consider to be energy-related. Based on an existing tool chain, their solution called Leafactor automatically refactor Java source code and xml layouts into the Eclipse IDE.…”

Section: Related Workmentioning

confidence: 99%

Enforcing green code with Android lint

Goaer

2020

Proceedings of the 35th IEEE/ACM International Conference on Automated Software Engineering Workshops

View full text Add to dashboard Cite

Nowadays, energy efficiency is recognized as a core quality attribute of applications (apps) running on Androidpowered devices constrained by their battery. Indeed, energy hogging apps are a liability to both the end-user and software developer. Yet, there are very few tools available to help developers increase the quality of their native code by ridding it of energy-related bugs. Android Studio is the official IDE for millions of developers worldwide and there's no better place to enforce green coding rules in everyday projects. Indeed, Android Studio provides a code scanning tool called Android lint that can be extended with lacking green checks in order to foster the design of more eco-responsible apps.

show abstract

Leafactor: Improving Energy Efficiency of Android Apps via Automatic Refactoring

Cited by 28 publications

References 6 publications

An Empirical Study on the Impact of Android Code Smells on Resource Usage

An Empirical Study on the Impact of Android Code Smells on Resource Usage

A Survey of Performance Optimization for Mobile Applications

Enforcing green code with Android lint

Contact Info

Product

Resources

About