8th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

Research Article

Adaptation of Single-user Multi-touch Components to Support Synchronous Mobile Collaboration

Download556 downloads
  • @INPROCEEDINGS{10.4108/icst.collaboratecom.2012.250449,
        author={Mauro Pichiliani and Celso Hirata},
        title={Adaptation of Single-user Multi-touch Components to  Support Synchronous Mobile Collaboration},
        proceedings={8th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing},
        publisher={IEEE},
        proceedings_a={COLLABORATECOM},
        year={2012},
        month={12},
        keywords={multi-touch mobile collaboration},
        doi={10.4108/icst.collaboratecom.2012.250449}
    }
    
  • Mauro Pichiliani
    Celso Hirata
    Year: 2012
    Adaptation of Single-user Multi-touch Components to Support Synchronous Mobile Collaboration
    COLLABORATECOM
    ICST
    DOI: 10.4108/icst.collaboratecom.2012.250449
Mauro Pichiliani1,*, Celso Hirata2
  • 1: ITA - Instituto Tecnologico de Aeronáutica
  • 2: ITA - Instituto Tecnologico de Aeronautica
*Contact email: pichiliani@uol.com.br

Abstract

Mobile applications, which include calendars, browsers, and text editors, are part of our lives nowadays. Most of the mobile applications are single user, i.e. they do not allow the cooperative work of group of users simultaneously. Adaptation is a technique to transform single user application into cooperative one. A form of adaptation is based on the reuse of the manufacturers’ SDKs (Software Development Kits). In general, adaptation is made manually; nonetheless, we conjecture that some automation is possible. This paper investigates this possibility for mobile applications by assuming that the target SDK’s components comply with certain design guidelines. We present a reference model to develop collaborative mobile groupware applications by the modification of multi-touch user interface components provided by the manufacturers’ SDKs. We also present a process to convert and adapt those components. We discuss two examples that illustrate our proposal.