Droidcon London 2010 - Create Killer Location Apps

Notas do Editor

2. Audience have used location services. How many used Rummble? Some already building location-centric apps. Some have apps and trying to work out how to integrate location.
3. Thanks for making first session. We living in the distant future... (according to Doc Brown) So let’s travel back in time to 1995 for some interactive trivia. I hope you’re awake!
4. 0.4% of world pop
5. 8.6% world pop
6. 8.6% world pop
7. Making assumption that most people on Twitter or other social networks have FB account. FB Launched in 2004, so < 3 years to get achieve same growth as internet.
8. Market size Google Maps, Local Search or Check-in service? Network effect... next slide
9. 1908 Theodore Vail, Bell Telephone annual report. Network effect much greater now - more connections, accelerated growth... ...building upon internet and social.
10. Rummble’s Q3 revenue.... 28.8% of world pop
11. Rummble’s Q3 revenue.... 28.8% of world pop
12. Rummble’s Q3 revenue.... 28.8% of world pop
18. Does this fit with your business?
19. Does this fit with your business?
20. Does this fit with your business?
21. Does this fit with your business?
22. Does this fit with your business?
23. Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas....
24. Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas....
26. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
27. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
28. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
29. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
30. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
31. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
32. What is your tolerance and implications on the UI? At what point do you reload data? Wifi - Works well in built up areas and indoors Cell ID - Works well, quite accurate with triangulation GPS - Long fix time, high accuracy, doesn’t work well in built-up areas.... Lead on to... but there’s one main alternative.
34. Crowd sourced historical population density API. Samsung - Android market rules.. ? check it out first
35. Crowd sourced historical population density API. Samsung - Android market rules.. ? check it out first
36. Crowd sourced historical population density API. Samsung - Android market rules.. ? check it out first
37. Crowd sourced historical population density API. Samsung - Android market rules.. ? check it out first
38. The Geolocation object is used by scripts to programmatically determine the location information associated with the hosting device. The location information is acquired by applying a user-agent specific algorithm, creating a Position object, and populating that object with appropriate data accordingly. Objects implementing the Navigator interface (e.g. the window.navigator object) must also implement the NavigatorGeolocation interface [NAVIGATOR]. An instance ofNavigatorGeolocation would be then obtained by using binding-specific casting methods on an instance of Navigator. 4.1 Privacy considerations for implementors of the Geolocation API User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users, as described below. The user interface must include the URI of the document origin [DOCUMENTORIGIN]. Those permissions that are acquired through the user interface and that are preserved beyond the current browsing session (i.e. beyond the time when the browsing context[BROWSINGCONTEXT] is navigated to another URL) must be revocable and user agents must respect revoked permissions.
39. The Geolocation object is used by scripts to programmatically determine the location information associated with the hosting device. The location information is acquired by applying a user-agent specific algorithm, creating a Position object, and populating that object with appropriate data accordingly. Objects implementing the Navigator interface (e.g. the window.navigator object) must also implement the NavigatorGeolocation interface [NAVIGATOR]. An instance ofNavigatorGeolocation would be then obtained by using binding-specific casting methods on an instance of Navigator. 4.1 Privacy considerations for implementors of the Geolocation API User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users, as described below. The user interface must include the URI of the document origin [DOCUMENTORIGIN]. Those permissions that are acquired through the user interface and that are preserved beyond the current browsing session (i.e. beyond the time when the browsing context[BROWSINGCONTEXT] is navigated to another URL) must be revocable and user agents must respect revoked permissions.
40. The Geolocation object is used by scripts to programmatically determine the location information associated with the hosting device. The location information is acquired by applying a user-agent specific algorithm, creating a Position object, and populating that object with appropriate data accordingly. Objects implementing the Navigator interface (e.g. the window.navigator object) must also implement the NavigatorGeolocation interface [NAVIGATOR]. An instance ofNavigatorGeolocation would be then obtained by using binding-specific casting methods on an instance of Navigator. 4.1 Privacy considerations for implementors of the Geolocation API User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users, as described below. The user interface must include the URI of the document origin [DOCUMENTORIGIN]. Those permissions that are acquired through the user interface and that are preserved beyond the current browsing session (i.e. beyond the time when the browsing context[BROWSINGCONTEXT] is navigated to another URL) must be revocable and user agents must respect revoked permissions.
41. The Geolocation object is used by scripts to programmatically determine the location information associated with the hosting device. The location information is acquired by applying a user-agent specific algorithm, creating a Position object, and populating that object with appropriate data accordingly. Objects implementing the Navigator interface (e.g. the window.navigator object) must also implement the NavigatorGeolocation interface [NAVIGATOR]. An instance ofNavigatorGeolocation would be then obtained by using binding-specific casting methods on an instance of Navigator. 4.1 Privacy considerations for implementors of the Geolocation API User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users, as described below. The user interface must include the URI of the document origin [DOCUMENTORIGIN]. Those permissions that are acquired through the user interface and that are preserved beyond the current browsing session (i.e. beyond the time when the browsing context[BROWSINGCONTEXT] is navigated to another URL) must be revocable and user agents must respect revoked permissions.
42. The Geolocation object is used by scripts to programmatically determine the location information associated with the hosting device. The location information is acquired by applying a user-agent specific algorithm, creating a Position object, and populating that object with appropriate data accordingly. Objects implementing the Navigator interface (e.g. the window.navigator object) must also implement the NavigatorGeolocation interface [NAVIGATOR]. An instance ofNavigatorGeolocation would be then obtained by using binding-specific casting methods on an instance of Navigator. 4.1 Privacy considerations for implementors of the Geolocation API User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users, as described below. The user interface must include the URI of the document origin [DOCUMENTORIGIN]. Those permissions that are acquired through the user interface and that are preserved beyond the current browsing session (i.e. beyond the time when the browsing context[BROWSINGCONTEXT] is navigated to another URL) must be revocable and user agents must respect revoked permissions.
43. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
44. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
45. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
46. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
47. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
48. 1 = UTC(universal time, coordinated) of position fix 2 = Data status (A=good, V=navigation receiver warning) 3 = Current Latitude 4 = North/South in Latitude Hemisphere 5 = Current Longitude 6 = East/West in Longitude Hemisphere 7 = Speed over ground in knots 8 = (Direction of travel N:0°, E:90°, S:180°, W:270°) 9 = UT DateStamp 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = East/West 12 = Checksum
49. So you’ve established the user location? What next?
50. Context - time, historical activity (user and everyone), social connections, etc..
51. Context - time, historical activity (user and everyone), social connections, etc..
52. Context - time, historical activity (user and everyone), social connections, etc..
53. Context - time, historical activity (user and everyone), social connections, etc..
54. Context - time, historical activity (user and everyone), social connections, etc..
55. Context - time, historical activity (user and everyone), social connections, etc..
56. Context - time, historical activity (user and everyone), social connections, etc..
57. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
58. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
59. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
60. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
61. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
62. Cold start problem not having Commercial license expensive - especially when location isn’t core and you want to scale globally. We’ve looked at available OS solutions (note examples) and the quality is bad. Scraping can be more expensive and time consuming. Can run into legal issues. Quality? Unified open location DB
63. Used to create boundaries, also contains some POI data....
69. Levels the playing field as far as check-ins are concerned... Can’t input lat,long yet...
70. Index, interpret and consume location Cloud infrastructure
71. Data Marketplace Spotrank
75. Quality of response fine for most apps, but will vary between services. Geocode on the client side where possible - i.e. use the Javascript SDK. List<Address>
76. Used to cost a fortune. People usually want to know how to find a place, but best to export leave this to Google Maps... Can get Bing tiles???
78. Group notificationsSimple to customise / turn off via app
82. To summarise
83. Are you average? Do you always like what everyone else likes? In many cases a rating derived from “an average” becomes meaningless.
84. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
85. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
86. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
87. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
88. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
89. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
90. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
91. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
92. To solve the problem, we had to come up with a new way to filter the noise & deliver relevant content. This was the birth of our algorithm.
93. This was the birth of our algorithm.
94. Then we had to build it.... Simple explanation follows.
95. Then we had to build it.... Simple explanation follows.
96. Then we had to build it.... Simple explanation follows.
97. Then we had to build it.... Simple explanation follows.
98. Then we had to build it.... Simple explanation follows.
99. Then we had to build it.... Simple explanation follows.
100. Then we had to build it.... Simple explanation follows.
101. Then we had to build it.... Simple explanation follows.
102. Then we had to build it.... Simple explanation follows.
103. Then we had to build it.... Simple explanation follows.
104. Then we had to build it.... Simple explanation follows.
105. Then we had to build it.... Simple explanation follows.
106. Then we had to build it.... Simple explanation follows.
107. Then we had to build it.... Simple explanation follows.
114. Greater reach, more content
115. Greater reach, more content
116. Greater reach, more content
117. Greater reach, more content
119. 450 average tweets a day from NYC alone, which comment on a venue, bar or restaurant. We’re currently processing ½ million tweets a day, from just 4 cities – San Francisco, Austin, New York, and London
120. Commercial rationale?
126. ...so come “swing” with us and not sound *too* strange.
127. ...so come “swing” with us and not sound *too* strange.
128. ...so come “swing” with us and not sound *too* strange.
129. ...so come “swing” with us and not sound *too* strange.
130. ...so come “swing” with us and not sound *too* strange.
136. Long tail graph – easy example; blue i regular bookshops, red is amazon.