Explore chapters and articles related to this topic
Pervasive Application Development Approaches and Pitfalls
Published in Syed Ijlal Ali Shah, Mohammad Ilyas, Hussein T. Mouftah, Pervasive Communications Handbook, 2017
Guruduth Banavar, Norman Cohen, Danny Soroker
A more widely used approach evolved, in which the view aspects of an application are conveyed in a device-independent representation. This device-independent representation describes the intent behind the user interaction within a view component (such as a page), rather than the actual physical representation of a user-interface control. For example, the fact that an application requires users to input their ages is represented by a generic INPUT element with a range constraint; an adaptation engine determines, based on the target device characteristics, usability considerations, or user preferences, whether the INPUT element should be realized as a text field, a selection list, or even voice input. Several device-independent view representations have evolved over the years, including User-Interface Markup Language (UIML) [11], Abstract User-Interface Markup Language (AUIML, previously known as Druid) [12], XForms [13], and Microsoft® ASP.NET Mobile Controls [14].
Accessible Ubiquitous Services for Supporting Daily Activities: A Case Study with Young Adults with Intellectual Disabilities
Published in International Journal of Human–Computer Interaction, 2019
Amaia Aizpurua, Raúl Miñón, Borja Gamecho, Idoia Cearreta, Myriam Arrue, Nestor Garay-Vitoria
The Egoki-automated user-tailored interface generator was developed with the aim of creating user interfaces tailored to the user and device features. It requires a logical description of the user interface and the provision of suitable multimodal interaction resources. In order to provide the logical description and to univocally specify the functionality of the user interface, a User Interface Description Language is required. For Egoki, we adopted User Interface Markup Language (UIML) (Phanouriou, 2000) because it includes the necessary mechanisms to map different types of resources to each interaction element (pictogram, text, audio, etc.) giving us an effective way to provide multimodality in the user interfaces (Gamecho et al., 2015). The accessible final user interface is automatically generated from that formal description, also taking into account the information about the user’s characteristics that is stored in an ontology specifically developed for this system and named EGONTO (see Figure 1). The EGONTO ontology includes three main models: the user model describing the interaction abilities (cognitive, physical, sensory) of individuals, the device model specifying software and hardware components of their device, and the adaptations model specifying content, presentation, and navigation adaptation techniques for user-tailored interfaces. Some generic rules are also included to cover the needs of specific groups of people with special needs (such as vision, hearing, cognitive, and motor impairments). The set of interface adaptations to be put in place by the Egoki system for creating an adapted user interface is the result of applying these reasoning rules.
EduGene: A UIDP-Based Educational App Generator for Multiple Devices and Platforms
Published in International Journal of Human–Computer Interaction, 2019
Cesar Augusto Cortes-Camarillo, Giner Alor-Hernández, Laura Nely Sánchez-Morales, Viviana Yarel Rosales-Morales, Lisbeth Rodríguez-Mazahua, José Luis Sánchez-Cervantes
Shahzad (2017) presented a simple, interactive, and browser-based Web application that was developed by using one of the latest Web development frameworks. Finally, Sayih and Brggemann-Klein (2016) proposed an XML-based solution for Web app development by using a set of XML technologies, including extensible hypertext markup language (XHTML) and XML forms language (XForms), scalable vector graphics (SVG), CSS, and user interface markup language (UIML). Both XHTML and XForms were used for data access and menus implementation, whereas SVG were used to display the graphical elements. Finally, CSS were used for the formatting and UIML for the graphical user interface design.