GeoLocal APIs unencumbering the  GeoLocal ecosystem Tyler Bell 14 September 2010 [email_address] Twitter: @twbell
Local Ecosystem Tyler Bell | tylerwbell@gmail.com | @twbell Interconnected resources that facilitate an informed, real-wor...
GeoLocal Tyler Bell | tylerwbell@gmail.com | @twbell Built Environment and AR Daily Deals Places and Listings Maps Utiliti...
Obligatory NASCAR Logo Montage Tyler Bell
Three Ways In Tyler Bell | tylerwbell@gmail.com | @twbell Application API Crawled Content Contribution To Local Ecosystem
Monday: TechCrunch/SimpleGeo Tyler Bell | tylerwbell@gmail.com | @twbell http://techcrunch.com/2010/09/13/what-is-it-you-d...
Piñata Tyler Bell | tylerwbell@gmail.com | @twbell Marketing (paper maché) API (candy) http://www.flickr.com/photos/esquip...
Tyler Bell | tylerwbell@gmail.com | @twbell APIs are the soul of a product
Source and Crawled Content Tyler Bell | tylerwbell@gmail.com | @twbell robots.txt is hugely insightful as is ‘viewing sour...
Example: Google Places PM <ul><li>“ We are going to focus initially on  check-in applications  [and] have now begun reachi...
Example: Google Places API TOS <ul><li>Applications  may not store  any Place data permanently except References and IDs. ...
Product Design Philosophy Tyler Bell | tylerwbell@gmail.com | @twbell The Hallway
No Doors http://www.flickr.com/photos/raulc/4429603/ Product does not facilitate new approaches, applications, or business...
Multiple Product Options http://www.flickr.com/photos/brentdanley/211734796/ Product creates multiple new opportunities fo...
A Look into some Local APIs Tyler Bell | tylerwbell@gmail.com | @twbell Short commentary  on what APIs reveal (now, not pl...
Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Ease of check-in at expense of data accuracy (this is OK, and worked w...
Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Only user names exposed to crawlers </li></ul><ul><li>Massive API pres...
Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>No ‘place pages’, therefore no  crawled metadata </li></ul><ul><li>Twe...
Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Hcard encoding on listings (nice) </li></ul><ul><li>FB Like Button </l...
Tyler Bell | tylerwbell@gmail.com | @twbell foursquare:venue=516723 Krohn Conservatory <ul><li>Machine tags allow cross-re...
Wrap Up: Use of Wire <ul><li>Razorwire v. Datawire  </li></ul>Tyler Bell | tylerwbell@gmail.com | @twbell
Datawire Tyler Bell | tylerwbell@gmail.com | @twbell http://www.flickr.com/photos/tigerplish/250836258/ Connect  and Plumb
Razorwire Tyler Bell | tylerwbell@gmail.com | @twbell http://www.flickr.com/photos/mightyboybrian/113445631/ Partition and...
Thank You Tyler Bell | tylerwbell@gmail.com | @twbell [email_address] @twbell http://radar.oreilly.com/tylerb/
Upcoming SlideShare
Loading in …5
×

GeoLocal APIs: unencumbering the geolocal ecosystem

954 views
883 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
954
On SlideShare
0
From Embeds
0
Number of Embeds
38
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Carl Shapiro and Hal Varian – network effect
  • Logo Montage
  • API as Product Soul
  • Robots.txt shows (in addition to ‘view source’) how a company wants to interface with the Open Web
  • Some products have only one outcome, but do not enable other connections
  • Others enable new opportunities, some as yet unknown
  • User experience at expense of all else Design reveals no initial plans forinteraction with other services
  • A reviews site with social elements superficially added later
  • GeoLocal APIs: unencumbering the geolocal ecosystem

    1. 1. GeoLocal APIs unencumbering the GeoLocal ecosystem Tyler Bell 14 September 2010 [email_address] Twitter: @twbell
    2. 2. Local Ecosystem Tyler Bell | tylerwbell@gmail.com | @twbell Interconnected resources that facilitate an informed, real-world consumer experience… The Local Ecosystem http://www.flickr.com/photos/leafy/3826214063/ and the value of a product is proportional to how many other products it communicates with
    3. 3. GeoLocal Tyler Bell | tylerwbell@gmail.com | @twbell Built Environment and AR Daily Deals Places and Listings Maps Utilities, Routing, Geocoding Social Location
    4. 4. Obligatory NASCAR Logo Montage Tyler Bell
    5. 5. Three Ways In Tyler Bell | tylerwbell@gmail.com | @twbell Application API Crawled Content Contribution To Local Ecosystem
    6. 6. Monday: TechCrunch/SimpleGeo Tyler Bell | tylerwbell@gmail.com | @twbell http://techcrunch.com/2010/09/13/what-is-it-you-do-the-need-for-simplicity/ A: See our API docs…. Q: What is it you do? This is the only appropriate answer to a developer
    7. 7. Piñata Tyler Bell | tylerwbell@gmail.com | @twbell Marketing (paper maché) API (candy) http://www.flickr.com/photos/esquipulas/561125635/
    8. 8. Tyler Bell | tylerwbell@gmail.com | @twbell APIs are the soul of a product
    9. 9. Source and Crawled Content Tyler Bell | tylerwbell@gmail.com | @twbell robots.txt is hugely insightful as is ‘viewing source’ … both make for lousy presentations
    10. 10. Example: Google Places PM <ul><li>“ We are going to focus initially on check-in applications [and] have now begun reaching out to developers” </li></ul>Tyler Bell | tylerwbell@gmail.com | @twbell http://googlegeodevelopers.blogspot.com/2010/07/checking-in-with-places-api.html - Google Maps API Product Manager
    11. 11. Example: Google Places API TOS <ul><li>Applications may not store any Place data permanently except References and IDs. </li></ul><ul><li>Place data cannot be redistributed via your own API </li></ul><ul><li>May only be used in conjunction with displaying results on a Google map </li></ul><ul><li>Using Place data without displaying a map for which Place data was requested is prohibited . </li></ul><ul><li>May only be used in response to end user actions . </li></ul><ul><li>So there. </li></ul>Tyler Bell | tylerwbell@gmail.com | @twbell Paraphrased from http://code.google.com/apis/maps/documentation/places/
    12. 12. Product Design Philosophy Tyler Bell | tylerwbell@gmail.com | @twbell The Hallway
    13. 13. No Doors http://www.flickr.com/photos/raulc/4429603/ Product does not facilitate new approaches, applications, or business models
    14. 14. Multiple Product Options http://www.flickr.com/photos/brentdanley/211734796/ Product creates multiple new opportunities for exploration, integration and experimentation
    15. 15. A Look into some Local APIs Tyler Bell | tylerwbell@gmail.com | @twbell Short commentary on what APIs reveal (now, not planned roadmap or intentions)
    16. 16. Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Ease of check-in at expense of data accuracy (this is OK, and worked well) </li></ul><ul><li>Massive dupe prob – solvable. Larger issue of traction has been addressed </li></ul><ul><li>Search provides no name-to-venue disambiguation </li></ul><ul><li>Robots.txt: restricts websearch </li></ul>http://aboutfoursquare.com/superusers-mislocated-venues/
    17. 17. Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Only user names exposed to crawlers </li></ul><ul><li>Massive API presence (of course) </li></ul><ul><li>Does not employ own metadata standards – see API note above </li></ul><ul><li>Robots.txt: heavy restrictions – again, pushing for API use v. crawled content </li></ul>
    18. 18. Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>No ‘place pages’, therefore no crawled metadata </li></ul><ul><li>Tweets from 4sq check-ins are tied to a Twitter place – done via BD rather than API </li></ul><ul><li>Three geo endpoints in API: nearby, details, and rev. geocode </li></ul><ul><li>Place serves now as tweet-centric hub – more certainly coming </li></ul>
    19. 19. Tyler Bell | tylerwbell@gmail.com | @twbell <ul><li>Hcard encoding on listings (nice) </li></ul><ul><li>FB Like Button </li></ul><ul><li>No venue resolution on search API </li></ul><ul><li>Literally impersonal: no people parameters in API </li></ul><ul><li>robots.txt contains ‘three laws of robotics’ (geek cred) </li></ul>
    20. 20. Tyler Bell | tylerwbell@gmail.com | @twbell foursquare:venue=516723 Krohn Conservatory <ul><li>Machine tags allow cross-reference into any namespace (incl. OSM) </li></ul><ul><li>Huge API </li></ul><ul><li>But also indexed and discoverable across search </li></ul>http://www.flickr.com/photos/chrisirmo/4560462516/
    21. 21. Wrap Up: Use of Wire <ul><li>Razorwire v. Datawire </li></ul>Tyler Bell | tylerwbell@gmail.com | @twbell
    22. 22. Datawire Tyler Bell | tylerwbell@gmail.com | @twbell http://www.flickr.com/photos/tigerplish/250836258/ Connect and Plumb
    23. 23. Razorwire Tyler Bell | tylerwbell@gmail.com | @twbell http://www.flickr.com/photos/mightyboybrian/113445631/ Partition and Control
    24. 24. Thank You Tyler Bell | tylerwbell@gmail.com | @twbell [email_address] @twbell http://radar.oreilly.com/tylerb/

    ×