<$BlogRSDUrl$>

Every Friday I pick a paper from the ACM Digital Library that is found by the search term +connected +2005 +"mobile device" +"user interface", and write a brief discussion of it. Why? Because it makes me actually read them.

virtual journal club: "Connected Mobile Devices UI"
Friday, April 30, 2004
MIRES: an information exchange system for mobile phones  
Link

Qing Li City University of Hong Kong
Xiang Li City University of Hong Kong
Jian Zhai City University of Hong Kong
Liu Wenyin City University of Hong Kong

Symposium on Applied Computing archive
Proceedings of the 2004 ACM symposium on Applied computing
Nicosia, Cyprus
SESSION: Mobile computing and applications (MCA)
Pages: 1196 - 1200
Year of Publication: 2004
ISBN:1-58113-812-1

Abstract:
Mobile computing has been studied in the past few years on many respects: adaptive application, mobility model, data access and so on. However, most research aim at a general computing framework but not focus on a specific device, for example, mobile phone. Mobile phones are special due to some constraints compared with other devices and they currently serve as no more than passive terminals to a large extent. At the same time, mobile phones are probably the most popular device today. This paper describes an operative resource sharing model in the context of MIRES - a Mobile Information Resource Exchange System which facilitates convenient resource sharing among mobile phones. Techniques from distributed database systems are combined with such wireless technologies as GPRS and J2ME. With the versatile facilities of MIRES, a mobile phone user can easily share his/her personal resources or get others' resources at his/her own will anytime and anywhere.

My Discussion
The ideas behind the infrastructure are intruiging -- basically creating repositories that are mirror images of the resources stored on the phone, and then allowing these images to referr to resources on other mirror images and then updating the phones -- but no case is made why this infrastructure is optimized or specific to mobile phones. The writers claim that it is in the beginning of the paper, and it would be interesting to see how, but they just state the structure of the repositories and the available operations, not how enables ease-of-use on mobile phones. Their infrastructure does acknowledge and work with the fact that connections are not stable or always on.

Friday, April 09, 2004
UbiCollab: collaboration support for mobile users 
Link

Monica Divitini IDI, NTNU, Trondheim, Norway
Babak A. Farshchian Telenor R&D, Trondheim, Norway
Haldor Samset Telenor R&D, Trondheim, Norway

Symposium on Applied Computing
Proceedings of the 2004 ACM symposium on Applied computing
Nicosia, Cyprus
SESSION: Mobile computing and applications (MCA)
Pages: 1191 - 1195
Year of Publication: 2004
ISBN:1-58113-812-1

Abstract:
Shared workspaces have emerged as one of the most successful applications of computer supported cooperative work (CSCW). Important aspects of shared workspaces are presence and awareness information, flexible sharing of work material, and support for communication among group members. One of the shortcomings of existing shared workspaces is their lack of support for mobility. In this paper we will discuss the need for mobile shared workspaces as well as an experimental platform for ubiquitous collaboration and a number of shared workspace implementations for both formal and informal collaboration.

My Discussion:
This papwer describes the conceptual architecture of a collaborative work system in which users can create tasks, create presence-enhanced buddy-lists, share task-related documents between the buddies, and use multiple channels to communicate. The structure of the paper justifies the flexibility of the design by introducing a scenario of mobile collaboration using desktops and handhelds. However, the writers engage in some false advertising: while in the first section they promise to "address the challenges related to developing mobile collaboration environments", the actual description of the scenario or resulting system barely reflects anything about the constraints of working with current mobile devices. It seems the handsets the UbiCollab creators are targetting have no bandwidth problems, easily support running a larger external screen to show downloaded documents while also making calls, sending SMSes, checking up on people's presence, and being logged into the server, without actually having any UI issues of managing all this, or connectivity issues of dropped voice or data connections, which are the first things that I think of when addressing the challenges of developing environments to run on mobile phones.
I think I want one of the handsets the UbiCollab people are using.

Friday, April 02, 2004
Mobile interfaces to computational, data, and service grid systems 
Link

Mauro Migliardi University of Genoa, Genoa, Italy
Muthucumaru Maheswaran University of Manitoba and TRLabs, Winnipeg, Canada
Balasubramaniam Maniymaran University of Manitoba and TRLabs, Winnipeg, Canada
Paul Card University of Manitoba and TRLabs, Winnipeg, Canada
Farag Azzedin University of Manitoba and TRLabs, Winnipeg, Canada

ACM SIGMOBILE Mobile Computing and Communications Review
Volume 6 , Issue 4 (October 2002)
Pages: 71 - 73
Year of Publication: 2002

Abstract:
This article briefly describes the issues related to providing mobile access to computational, data, and service Grids. Then it describes our preliminary efforts to enhance computational and service Grids to handle mobile access. In particular, we focus on how the HARNESS mobile extensions project approaches the problem of enhancing Grid computers with mobile access and we describe how the InviNet project provides access to service Grids with consistent quality of service.

My Discussion:
Two page papaer, just provides an overview of the system the writers are working, plus some useful terminology. What has been written about how they see mobile devices interacting with their computational girds shows a sound understanding of what mobile systems can bring and what constraints (network drops, low bandwidth) they are under. It would be interesting to look up their references for other work they have done.

This page is powered by Blogger. Isn't yours?