Successfully reported this slideshow.

LUCID demonstrator: Co-loco

525 views

Published on

An experiment in geosocialising on mobile phones

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

LUCID demonstrator: Co-loco

  1. 1. A knowledge-sharing event investigating current opportunities and the future of context-aware information delivery on mobile devices. CO-LOCO a geo-socialising application
  2. 2. Aims <ul><li>explore geo-socialising applications </li></ul><ul><li>explore co-located people and place discovery: </li></ul><ul><li>enable users to tag locations – create POIs </li></ul><ul><li>enable users to interact with each other – via messaging and via comments on POIs </li></ul><ul><li>game aspect – interaction means points </li></ul>
  3. 3. Approach <ul><li>client-server interaction </li></ul><ul><li>- XML (client-agnostic) </li></ul><ul><li>client side </li></ul><ul><li>- JME (well supported) </li></ul><ul><li>- KXML mobile XML parser ~ small footprint </li></ul><ul><li>- MobiMaps ~ openstreetmaps flavour </li></ul><ul><li>- GPS location </li></ul>
  4. 4. Demonstrator: overview
  5. 5. Demonstrator: overview
  6. 6. Demonstrator Overview <ul><li>users sign up / log in </li></ul><ul><li>map view of area – including UGC POIs and known users (“friends”) </li></ul><ul><li>list view too </li></ul><ul><li>Users can: </li></ul><ul><li>contribute POIs (text; images) </li></ul><ul><li>comment </li></ul><ul><li>messaging – direct to friend or to all </li></ul><ul><li>gain/see points </li></ul>
  7. 7. Issues <ul><li>usability of mapping apps on small screens </li></ul><ul><li>high data overhead (map tiles) – FIZ pinholes </li></ul><ul><li>user acceptance issues - privacy </li></ul><ul><ul><li>- only friends can see each other’s location </li></ul></ul><ul><ul><li>- strangers only know that X is in the area </li></ul></ul><ul><ul><li>- only friends can directly message each other </li></ul></ul><ul><ul><li>- blacklisting if necessary </li></ul></ul>
  8. 8. Conclusions <ul><li>tech barriers: JME implementations – not all JSRs (i.e. java libraries for location, multimedia etc.); can be difficult to find out what JSRs are implemented. </li></ul><ul><li>generic JME UI toolkit inferior to e.g. LWUIT (L ightweight UI Toolkit ) </li></ul><ul><li>usability and privacy are key </li></ul><ul><li>consider caching (lower data transfer) </li></ul>
  9. 9. Next steps <ul><li>Improve UI </li></ul><ul><li>larger scale user testing (over FIZ) </li></ul><ul><li>explore pervasive game applications </li></ul><ul><li>alternate mapping – map source; map contents </li></ul><ul><li>(web) front-end = geoblog? </li></ul><ul><li>caching / strategies for popularity! </li></ul>

×