Sponsors
  • Etelos
  • IBM
  • Microsoft
  • Adobe Systems, Inc.
  • Cynergy
  • Nokia
  • Openmaru Studio
  • WebEx
  • AOL
  • Citrix Systems
  • Coghead
  • Confident Technologies
  • Disney
  • Disney
  • EffectiveUI
  • F5 Networks
  • HCL Technologies
  • Intuit Quickbase
  • Oracle
  • S60
  • Salesforce.com
  • Spinscape
  • Sun Microsystems
  • Symphoniq Corporation
  • TeleAtlas
  • Yahoo! Inc.
  • Amazon Web Services
  • Atlassian Software Systems
  • awareness
  • BroadSoft
  • Curl
  • Denodo
  • Dixero
  • Force10 Networks
  • Humanix Inc.
  • Intel
  • JackBe
  • Jaduka
  • Jive Software
  • Juniper Networks
  • Kapow Technologies
  • Keynote Systems
  • Leverage Software
  • LiquidApps
  • LithiumTechnologies
  • LongJump
  • Morfik
  • Mzinga
  • NeuStar
  • Octopz
  • ONEsite
  • OpSource
  • Panther Express
  • Profy
  • Real Time Content
  • Rearden
  • Rearden Commerce
  • Remy
  • Reply
  • spigit
  • StreamVerse, Inc.
  • StrikeIron
  • XBOSoft
  • Znak
  • O'Reilly Alpha Tech Ventures
  • Panorama Capital
  • ACM Queue
  • Berlin Partner
  • BlogHer
  • Business Marketing Association
  • Dr. Dobbs
  • Fast Company
  • GigaOM
  • Juniper Research
  • Mashable
  • MSDN Magazine
  • NewTeeVee
  • Revenue Magazine
  • TechNet
  • Technorati
  • Topix
  • Webware
  • Wired
  • WOW

Sponsor & Exhibitor Opportunities

Vicki Sanders
415-947-6107
vsanders@techweb.com

Download the Web 2.0 Expo San Francisco Sponsor/Exhibitor Prospectus

Media Sponsor Opportunities

Liliana Arancibia
415-947-6179
larancibia@cmp.com

Speaker / Program Ideas

Have a suggestion for a speaker or topic at Web 2.0 Expo San Francisco? Send an email to: sf-idea@web2expo.com

Press/Media Inquiries

confpr@oreilly.com

or

Natalia Wodecki
415-947-6762
NWodecki@cmp.com

Contact Us

View a complete list of Web 2.0 Expo contacts.


Design Your API: Learnings from Twitter and Stamen

Alex Payne (Twitter), Michal Migurski (Stamen Design)
Development
Location: 2003

Web 2.0 owes much of its success to APIs: protocols to create, distribute, update, and modify the valuable data that comprises the Web. Twitter’s Alex Payne and Stamen’s Michal Migurski will discuss the design of web service APIs from the dual perspectives of client and provider, outlining best practices and cautioning against worst cases.

Topics covered will include personal experiences in supporting API developer communities, RESTful architecture, data interchange formats, design trade-offs, strategies for development, surviving rapid growth, making considerations for client software, and more.

War stories will be shared, examples given, and beautiful visualizations shown.

Photo of Alex Payne

Alex Payne

Twitter

Alex Payne is an engineer at Twitter, a social network of individuals sharing short status updates via the web, SMS, IM, and an extremely popular API. Since taking on the support and development of Twitter’s API, the service has grown to hundreds of millions of requests per day. Alex’s background is in web application development and information security, and his code has powered mission-critical operations, political campaigns, and non-profit initiatives. Alex lives and works in San Francisco.

Photo of Michal Migurski

Michal Migurski

Stamen Design

Michal Migurski is a technology director and partner in San Francisco design firm Stamen. Michal architects the technical aspects of Stamen’s work, moving comfortably from active participation in the visual design process, designing database schemas and API’s, to creating the dynamic applications and visualizations Stamen is known for. Michal has participated in projects for clients including BMW, MoveOn.org, Digg.com, Yahoo!, The Exploratorium, and numerous others. Michal’s API-specific work has included URL and format design for Digg and Pownce RESTful services and purpose-built API’s for a variety of research and commercial projects.