Performance and Programming Effort Trade-offs of Android Persistence Frameworks

TL;DR

This paper systematically compares the performance and programming effort of eight Android persistence frameworks to guide developers in selecting the most suitable one based on energy, speed, and ease of use.

Contribution

It provides the first comprehensive analysis of energy, execution time, and programming effort trade-offs among popular Android persistence frameworks.

Findings

Identifies frameworks with optimal energy efficiency.

Highlights frameworks with minimal programming effort.

Provides practical guidelines for framework selection.

Abstract

A fundamental building block of a mobile application is the ability to persist program data between different invocations. Referred to as \emph{persistence}, this functionality is commonly implemented by means of persistence frameworks. Without a clear understanding of the energy consumption, execution time, and programming effort of popular Android persistence frameworks, mobile developers lack guidelines for selecting frameworks for their applications. To bridge this knowledge gap, we report on the results of a systematic study of the performance and programming effort trade-offs of eight Android persistence frameworks, and provide practical recommendations for mobile application developers.