TY - CHAP A1 - Oppermann, Leif A1 - Jacobs, R. A1 - Watkins, M. A1 - Shackford, R. A1 - Tycowicz, Christoph von A1 - Wright, M. A1 - Capra, M. A1 - Greenhalgh, Chris A1 - Benford, Steve T1 - Love City: A Text-Driven, Location-Based Mobile Phone Game Played Between 3 Cities T2 - Pervasive Gaming Applications - A Reader for Pervasive Gaming Research Y1 - 2007 SN - 978-3-8322-6224-2 VL - 2 SP - 285 EP - 312 PB - Shaker Verlag ER - TY - CHAP A1 - Greenhalgh, Chris A1 - Benford, Steve A1 - Drozd, Adam A1 - Flintham, Martin A1 - Hampshire, Alastair A1 - Oppermann, Leif A1 - Smith, Keir A1 - Tycowicz, Christoph von T1 - EQUIP2: A Platform for Mobile Phone-based Game Development T2 - Concepts and Technologies for Pervasive Games - A Reader for Pervasive Gaming Research Y1 - 2007 SN - 978-3-8322-6223-5 VL - 1 SP - 153 EP - 178 PB - Shaker Verlag ER - TY - CHAP A1 - Greenhalgh, Chris A1 - Benford, Steve A1 - Drozd, Adam A1 - Flintham, Martin A1 - Hampshire, Alastair A1 - Oppermann, Leif A1 - Smith, Keir A1 - Tycowicz, Christoph von T1 - Addressing Mobile Phone Diversity in Ubicomp Experience Development T2 - UbiComp 2007: Ubiquitous Computing, 9th International Conference N2 - Mobile phones are a widely-available class of device with supporting communications infrastructure which can be appropriated and exploited to support ubicomp experiences. However mobile phones vary hugely in their capabilities. We explore how a single dimension of phone application type embodies the critical trade-off between capability and availability, i.e. between what can be done and the fraction of potential participants’ phones that can do this. We describe four different mobile phone ubicomp experiences that illustrate different points along this continuum (SMS, WAP/Web, and J2ME, Python and native applications) and the common software platform/toolkit, EQUIP2, that has been co-developed to support them. From this we propose four development strategies for addressing mobile phone diversity: prioritise support for server development (including web integration), migrate functionality between server(s) and handset(s), support flexible communication options, and use a loosely coupled (data-driven and component-based) software approach. Y1 - 2007 U6 - https://doi.org/10.1007/978-3-540-74853-3_26 VL - 4717 SP - 447 EP - 464 ER -