The document discusses the limitations of building location-based services that solely focus on a user's location. It summarizes that location often fails to account for: 1) A user's preferences over proximity 2) The multi-layered nature of places in a person's life 3) A user's experience and knowledge 4) Relevance, timeliness, and meaningfulness of information 5) Appropriateness when considering privacy and data quality issues. The key message is that services should be built for people, not just locations, in order to provide truly useful and personalized information.

1. does location matter?

2. i am
@neal_lathia
university college london

4. i research
sensing (in) the city

5. with lots of data, coming from

7. what is so special about it?
focus on two buzz words

8. “smart cities” + “big data”

9. smart cities want to join the
BIG DATA hype.

10. what
services can
we build using
a city's data?

11. that's right,
location based
services

12. “ it is now commonplace for people
to retrieve the information they
need on demand
according to their location
- this workshop's description
”

13. today let's talk about
where location
FAILS
...and what really matters

14. “ it is now commonplace for people
to retrieve the information they
need on demand vs.
according to their location
- this workshop's description
”

15. in 5 points that say:
don't build for location,
build for the person

16. 1: The Infamous “Radius”

17. location based services remind me of

19. playing old-school video games. why?

20. that's you

21. that's the view of the world
your location-service gives you

22. that's where your
favourite band is
playing tonight

23. that's the
restaurant you
would love

24. that's the thing you
need right now

25. 1: the radius opts for laziness
(close) over preference (let's go!)
don't build for location, build for the person

26. 2: The Ontology of Location

27. sometimes i care about here:

29. sometimes, my city:

31. other times, other cities

33. or many cities

35. 2: information about “place” can
cover several layers
don't build for location, build for the person

36. 3: Discovery vs. History

37. e.g., i want a coffee

38. let's search...

39. 3: location ignores the users'
experience and knowledge
don't build for location, build for the person

40. 4: Relevance & Explanations

41. i don't commute with
the Central Line.

42. Dave C. isn't my friend :(

43. i was free 4 hours ago
too.

44. people who go
to train stations
go to China Town.

45. 4: location does not mean
relevant, timely, or meaningful
don't build for location, build for the person

46. 5: the data problem

47. social signalling
vs. location
quality

48. are all ratings
meaningful?

49. privacy nightmare

50. 5: “location data” doesn't mean
“appropriate”
don't build for location, build for the person

51. summary:
where location
FAILS

52. 1: the radius opts for laziness
(close) over preference (let's go!)

53. 2: information about “place” can
cover several layers

54. 3: location ignores the users'
experience and knowledge

55. 4: location does not mean
relevant, timely, or meaningful

56. 5: “location” doesn't mean
“appropriate”

57. don't build for
LOCATION
build for
PEOPLE

58. @neal_lathia
university college london
http://www.cs.ucl.ac.uk/staff/n.lathia