Tyler bell

24
Location Business Summit GeoLocal APIs unencumbering the GeoLocal ecosystem Tyler Bell 14 September 2010 [email protected] Twitter: @twbell

Transcript of Tyler bell

Page 1: Tyler bell

Location Business Summit

GeoLocal APIs

unencumbering theGeoLocal ecosystemTyler Bell

14 September 2010

[email protected]

Twitter: @twbell

Page 2: Tyler bell

Local Ecosystem

Interconnected resources that facilitate an

informed, real-world consumer

experience…

The Local Ecosystem

- 2 -Tyler Bell | [email protected] | @twbell http://www.flickr.com/photos/leafy/3826214063/

and the value of a product is proportional

to how many other products it

communicates with

Page 3: Tyler bell

GeoLocal

Built Environment and AR Daily Deals

Maps Utilities, Routing, Geocoding

- 3 -Tyler Bell | [email protected] | @twbell

Places and Listings

Maps Utilities, Routing, Geocoding

Social Location

Page 4: Tyler bell

Obligatory NASCAR Logo Montage

- 4 -Tyler Bell

Page 5: Tyler bell

Three Ways In

CrawledContent

- 5 -Tyler Bell | [email protected] | @twbell

Application

APIContribution

To Local

Ecosystem

Page 6: Tyler bell

Monday: TechCrunch/SimpleGeo

Q: What is it you do?

- 6 -Tyler Bell | [email protected] | @twbell

http://techcrunch.com/2010/09/13/what-is-it-you-do-the-need-for-simplicity/

A: See our API docs….

This is the only appropriate answer to a developer

Page 7: Tyler bell

PiñataMarketing (paper maché)

- 7 -Tyler Bell | [email protected] | @twbell

API (candy)

http://www.flickr.com/photos/esquipulas/561125635/

Page 8: Tyler bell

APIs are the soul of a product

- 8 -Tyler Bell | [email protected] | @twbell

They reveal its naked capabilities and the intentions of its creators

Page 9: Tyler bell

Source and Crawled Content

robots.txt is hugely insightful

as is ‘viewing source’

- 9 -Tyler Bell | [email protected] | @twbell

…both make for lousy presentations

Page 10: Tyler bell

Example: Google Places PM

“We are going to focus initially on check-in applications [and] have now begun

- 10 -

in applications [and] have now begun reaching out to developers”

Tyler Bell | [email protected] | @twbell

http://googlegeodevelopers.blogspot.com/2010/07/checking-in-with-places-api.html

- Google Maps API Product Manager

Page 11: Tyler bell

Example: Google Places API TOS

• Applications may not store any Place data permanently except References and IDs.

• Place data cannot be redistributed via your own API

• May only be used in conjunction with displaying

- 11 -

results on a Google map

• Using Place data without displaying a map for which Place data was requested is prohibited.

• May only be used in response to end user actions.

• So there.

Tyler Bell | [email protected] | @twbell

Paraphrased from http://code.google.com/apis/maps/documentation/places/

Page 12: Tyler bell

Product Design Philosophy

- 12 -Tyler Bell | [email protected] | @twbell

The Hallway

Page 13: Tyler bell

No Doors

Product does not facilitate new

approaches, applications, or

business models

- 13 -http://www.flickr.com/photos/raulc/4429603/

Page 14: Tyler bell

Multiple Product Options

- 14 -http://www.flickr.com/photos/brentdanley/211734796/

Product creates multiple new

opportunities for exploration, integration

and experimentation

Page 15: Tyler bell

A Look into some Local APIs

Short commentary

- 15 -Tyler Bell | [email protected] | @twbell

on what APIs reveal(now, not planned roadmap or intentions)

Page 16: Tyler bell

• Ease of check-in at expense of data accuracy (this is OK, and worked well)

• Massive dupe prob – solvable. Larger

- 16 -Tyler Bell | [email protected] | @twbell

– solvable. Larger issue of traction has been addressed

• Search provides no name-to-venue disambiguation

• Robots.txt: restricts websearchhttp://aboutfoursquare.com/superusers-mislocated-venues/

Page 17: Tyler bell

• Only user names exposed to crawlers

• Massive API presence

- 17 -Tyler Bell | [email protected] | @twbell

• Massive API presence (of course)

• Does not employ own metadata standards –see API note above

• Robots.txt: heavy restrictions – again, pushing for API use v. crawled content

Page 18: Tyler bell

• No ‘place pages’, therefore no crawled metadata

• Tweets from 4sq check-ins are tied to a Twitter place – done

- 18 -Tyler Bell | [email protected] | @twbell

Twitter place – done via BD rather than API

• Three geo endpoints in API: nearby, details, and rev. geocode

• Place serves now as tweet-centric hub –more certainly coming

Page 19: Tyler bell

• Hcard encoding on listings (nice)

• FB Like Button

- 19 -Tyler Bell | [email protected] | @twbell

• No venue resolution on search API

• Literally impersonal: no people parameters in API

• robots.txt contains ‘three laws of robotics’ (geek cred)

Page 20: Tyler bell

foursquare:venue=516723

Krohn Conservatory

• Machine tags allow

- 20 -Tyler Bell | [email protected] | @twbell

• Machine tags allow cross-reference into any namespace (incl. OSM)

• Huge API

• But also indexed and discoverable across searchhttp://www.flickr.com/photos/chrisirmo/4560462516/

Page 21: Tyler bell

Wrap Up: Use of Wire

- 21 -

Razorwire v. Datawire

Tyler Bell | [email protected] | @twbell

Page 22: Tyler bell

Datawire Connect and Plumb

- 22 -Tyler Bell | [email protected] | @twbell http://www.flickr.com/photos/tigerplish/250836258/

Page 23: Tyler bell

Razorwire Partition and Control

- 23 -Tyler Bell | [email protected] | @twbell http://www.flickr.com/photos/mightyboybrian/113445631/

Page 24: Tyler bell

Thank You

[email protected]

- 24 -Tyler Bell | [email protected] | @twbell

@twbell

http://radar.oreilly.com/tylerb/