Implications of HCI in energy consumption between native and rich-client applications for navigations widgets in tablets

Ana Belem Márquez Quintos, Amilcar Meneses Viveros, Erika Hernández Rubio

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

The mobile platforms could be classified among those using virtual machine and that not use to run native apps. A native app is developed in a specific way for an specific mobile platform. The Rich-Client Applications are structured multilayer form. Developers and users have the problem of working with the constraints of mobile devices such as the energy consumption. The developers have tried to do usercentered designs. Analyzes have been conducted to justify the feasibility of developing mobile device applications natively or rich-client. This paper presents a comparative study of navigation widget in rich-client applications against native iOS and Android applications is presented. The results presented do not make a quantitative comparison between native iOS and Android applications.

Original languageEnglish
Title of host publicationHCI International 2015 - Posters Extended Abstracts - International Conference, HCI International 2015, Proceedings
EditorsConstantine Stephanidis
PublisherSpringer Verlag
Pages32-38
Number of pages7
ISBN (Print)9783319213828
DOIs
StatePublished - 2015
Event17th International Conference on Human-Computer Interaction, HCI International 2015 - Los Angeles, United States
Duration: 2 Aug 20157 Aug 2015

Publication series

NameCommunications in Computer and Information Science
Volume529
ISSN (Print)1865-0929

Conference

Conference17th International Conference on Human-Computer Interaction, HCI International 2015
Country/TerritoryUnited States
CityLos Angeles
Period2/08/157/08/15

Fingerprint

Dive into the research topics of 'Implications of HCI in energy consumption between native and rich-client applications for navigations widgets in tablets'. Together they form a unique fingerprint.

Cite this