Design constraints on operational LBS

Abstract

In the last 15 years of accelerated digital technology evolution a well-established model of product and service development known as the hype cycle has been seen to effectively characterise the progress of specific technologies from birth to acceptance. LBS need to be assessed against this template and currently it can be argued that they are lying in the ‘Trough of disillusionment’. In order to ensure that LBS move through the cycle towards the ‘Plateau of productivity’, the emerging LBS interdiscipline needs an assessment of what is needed for LBS to succeed.

Drawing upon the experience of an EU research project ‘Webpark’ (http://www.webparkservices.info/) and two UK research projects Locus (http://www.locus.org.uk/) and LBS4all (http://www.lbs4all.org/), this paper will examine a design template for LBS focussed on operational requirements and constraints. This template focuses on the following interlocking requirements for:

• Mobile device memory, communication interfaces and positioning support

• operating systems for mobile devices and their customisation potential

• development platforms supporting real-time positioning and network-agnostic behaviour

• graphics technologies with performance and integration with development platforms

• data warehousing, GIS data integration and delivery to mobile devices

• human-computer interfaces with user acceptance

Examples will be given from design statements on the projects being undertaken at City University.

These factors reflect a technological view of the elements needed for the performance and functionality of LBS applications at a level of innovation likely to attract the consumer. The challenge for researchers is to demonstrate attractive potential applications, the challenge for the industry is to deliver the elements needed at a price the consumer and business users can accept. However, if either part in the equation is unrealistic, then LBS might not progress to achieve their potential.