UIML: an appliance-independent XML user interface language

Abrams, Marc D.; Phanouriou, Constantinos; Batongbacal, Alan; Williams, Stephen M.; Shuster, Jonathan E.

doi:10.1016/s1389-1286(99)00044-4

Cited by 259 publications

(130 citation statements)

References 4 publications

Supporting

Mentioning

124

Contrasting

Unclassified

Order By: Relevance

“…The intermediate UI form of Cloud Twin resembles the universal UI representations of independent UI models, such as those used in UIML [10] and the aforementioned PhoneGap [18]. UIML and PhoneGap enable platform independent design and development of user interfaces.…”

Section: Related Workmentioning

confidence: 99%

Cloud Twin: Native execution of android applications on the Windows Phone

Holder

Shah

Davoodi

et al. 2013

2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

Abstract-To successfully compete in the software marketplace, modern mobile applications must run on multiple competing platforms, such as Android, iOS, and Windows Phone. Companies producing mobile applications spend substantial amounts of time, effort, and money to port applications across platforms. Creating individual program versions for different platforms further exacerbates the maintenance burden. This paper presents Cloud Twin, a novel approach to natively executing the functionality of a mobile application written for another platform. The functionality is accessed by means of dynamic cross-platform replay, in which the source application's execution in the cloud is mimicked natively on the target platform. The reference implementation of Cloud Twin natively emulates the behavior of Android applications on a Windows Phone. Specifically, Cloud Twin transmits, via web sockets, the UI actions performed on the Windows Phone to the cloud server, which then mimics the received actions on the Android emulator. The UI updates on the emulator are efficiently captured by means of Aspect Oriented Programming and sent back to be replayed on the Windows Phone. Our case studies with third-party applications indicate that the Cloud Twin approach can become a viable solution to the heterogeneity of the mobile application market.

show abstract

Section: Related Workmentioning

confidence: 99%

Cloud Twin: Native execution of android applications on the Windows Phone

Holder

Shah

Davoodi

et al. 2013

2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

show abstract

“…describe UI in order to deal with sub-parts of former UI. The description of an UI both involves (1) description of its structure (like UIML [1], ALIAS [7], UsiXML [5] or MARIA [8]) and (2) the spatial positioning of these components (like in different layouts used in the UI toolkits).…”

Section: Related Workmentioning

confidence: 99%

OntoCompo: A Tool to Enhance Application Composition

Brel

Déry-Pinna

Renevier-Gonin

et al. 2011

Human-Computer Interaction – INTERACT 2011

View full text Add to dashboard Cite

Abstract. Mash-ups emerged through the web 2.0 to juxtapose several applications and use them together. The next step after juxtaposition is the composition of existing applications to build a new one. A solution of this being born need is the reuse of parts from formers applications. To perform this composition and reuse in an easy and comfortable way, we propose a tool based on several extensions of selection to help the developer during his composition.

show abstract

“…Abstract interface models [6,[8][9][10][11][12] are problematic when abstraction is such that there is no convenient implementation of the low-level interaction objects on a particular platform. A model must be defined to either restrict the set of objects to ones that are common across all platforms, or provide a wider set of objects to cover the variation in platform.…”

Section: Problems Of Abstract User Interface Modelsmentioning

confidence: 99%

“…Presenting a user interface for a UIML [11,12] specification on a specific platform involves more than selecting an appropriate widget representation. An interface structure that is defined canonically may fit one platform but not another.…”

Section: Problems Of Abstract User Interface Modelsmentioning

confidence: 99%

Using Interaction Style to Match the Ubiquitous User Interface to the Device-to-Hand

Gilroy

Harrison

2005

Engineering Human Computer Interaction and Interactive Systems

View full text Add to dashboard Cite

Abstract. Ubiquitous computing requires a multitude of devices to have access to the same services. Abstract specifications of user interfaces are designed to separate the definition of a user interface from that of the underlying service This paper proposes the incorporation of interaction style into this type of specification. By selecting an appropriate interaction style, an interface can be better matched to the device being used. Specifications that are based upon three different styles have been developed, together with a prototype StyleBased Interaction System (SIS) that utilises these specifications to provide concrete user interfaces for a device. An example weather query service is described, including specifications of user interfaces for this service that use the three different styles as well as example concrete user interfaces that SIS can produce. IntroductionThe increasing availability of personalized and ubiquitous technologies leads to the possibility that whatever the device-to-hand is, it becomes the way to access services and systems. Therefore, interfaces to services must be designed for a variety of different types of device from desktop systems to handheld or otherwise portable devices. Different styles of interaction often suit different devices most effectively. While the appearance of ubiquitous devices has brought forth a proliferation of innovative interactive techniques, the broad categories and aspects of style as, for example, identified by Newman and Lamming [1] can still be applied. While a keymodal interface may be appropriate for a mobile telephone, with its limited screen and restricted keypad, a direct manipulation (DM) interface may be appropriate for a device based around touch / pen interactive techniques, such as current models of palmtop or tablet PCs. Typically in such situations a different low-level interface will have to be designed separately for each device. It is possible that several interaction styles may have to be supported for different users or parts of the system on the same device. As new technologies evolve to meet the demands of ubiquitous computing additional styles will emerge. Style-specific design considerations normally take the form of guidelines, heuristics or ad-hoc rationalizations by designers [2]. Designs to support many devices may be facilitated by incorporating interaction style explicitly into an implementation. In this paper we demonstrate that incorporating style-level descriptions into a model of a user interface can give more flexibility than forcing a single user interface model on a heterogeneous selection of devices. This paper is concerned with an approach in which interaction with a service is bound to the features of the platform through a mediating style description. The aim is to support an interface that is appropriate given the technological constraints or opportunities afforded by the platform. In section 2 the approach to the style-based interaction system is contrasted with other approaches to platform independent service...

show abstract

UIML: an appliance-independent XML user interface language

Cited by 259 publications

References 4 publications

Cloud Twin: Native execution of android applications on the Windows Phone

Cloud Twin: Native execution of android applications on the Windows Phone

OntoCompo: A Tool to Enhance Application Composition

Using Interaction Style to Match the Ubiquitous User Interface to the Device-to-Hand

Contact Info

Product

Resources

About