![]() The experiments could not assert an inherent technological disadvantage of PWAs in contrast to other MCPD approaches when considering UI energy consumption. PWAs, albeit having a higher energy consumption than native apps, are a viable alternative to other mobile cross-platform development (MCPD) approaches. Native development shows the lowest energy consumption. ![]() The results based on sample and real-world apps show that the used development approach influences the energy footprint of a mobile app. Regarding execution environments, we also compared the energy consumption of PWAs executed in different web-browsers. Additionally, we extended our research by analyzing multiple real-world mobile apps to include a more practical perspective. For this, we implemented five versions of the same app with different development approaches and examined their energy footprint on two Android devices with four execution scenarios. As mobile apps are primarily interactive in nature, we focus on UI rendering and interaction scenarios. The goal of this study is to analyze the difference in energy consumption of PWAs compared to other mobile development approaches. As mobile devices are limited with respect to battery capacity, developers should keep the energy footprint of a mobile app as low as possible. Progressive Web Apps (PWAs) are a promising approach for developing mobile apps, especially when developing apps for multiple mobile systems. Hardware access (Rieger & Majchrzak, 2019), (Xanthopoulos & Xinogalos, 2013), device features (Latif et al., 2016), device API (Charkaoui et al., 2014), device resource support (Hudli et al., 2015), sensor data capture (Dhillon & Mahmoud, 2015), built-in features (Dalmasso et al., 2013), hardware sensors (Sommer & Krusche, 2013), mobile device functions (Vitols et al., 2013), platform-specific features (Heitkötter et al., 2013), APIs (Palmieri et al., 2012), accelerometer (Ciman & Gaggi, 2017) (Dhillon & Mahmoud, 2015) (Vitols et al., 2013), (Palmieri et al., 2012), (Ribeiro & da Silva, 2012), compass (Ciman & Gaggi, 2017) (Dhillon & Mahmoud, 2015), (Palmieri et al., 2012), proximity (Ciman & Gaggi, 2017), (Dhillon & Mahmoud, 2015), GPS (Ciman & Gaggi, 2017) (Que et al., 2016) (Dhillon & Mahmoud, 2015), (Ribeiro & da Silva, 2012), geolocation (Sommer & Krusche, 2013) (Vitols et al., 2013) (Palmieri et al., 2012), camera (Ciman & Gaggi, 2017) (Que et al., 2016) (Dhillon & Mahmoud, 2015) (Vitols et al., 2013), (Palmieri et al., 2012), (Ribeiro & da Silva, 2012), audio record (Ciman & Gaggi, 2017), microphone (Dhillon & Mahmoud, 2015), Bluetooth (Dhillon & Mahmoud, 2015) (Ohrt & Turau, 2012) (Palmieri et al., 2012), accelerator (Que et al., 2016), GPU acceleration (Dhillon & Mahmoud, 2015), light (Ciman & Gaggi, 2017), notification light activation (Dhillon & Mahmoud, 2015), noise cancelation microphone (Dhillon & Mahmoud, 2015), NFC (Dhillon & Mahmoud, 2015) (Palmieri et al., 2012), gyroscope (Dhillon & Mahmoud, 2015), barometer (Dhillon & Mahmoud, 2015), Wi-Fi positioning (Dhillon & Mahmoud, 2015), cellular positioning (Dhillon & Mahmoud, 2015), network (Sommer & Krusche, 2013) (Vitols et al., 2013), lowlevel networking (Dhillon & Mahmoud, 2015), connection (Palmieri et al., 2012), (hardware) buttons (Sommer & Krusche, 2013), device (information) (Palmieri et al., 2012) A3 System integration (Rieger & Majchrzak, 2019), Social APIs, Cloud APIs (Dhillon & Mahmoud, 2015), backend communication (Dalmasso et al., 2013), corporate identity (Sommer & Krusche, 2013) continued on following page.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |