A brief presentation to the San Francisco Mobile 2.0 Meetup on what 2009 has in store for the Twitter API and related technologies.

1. THE TWITTER API
WHERE’S IT GOING?
Presented to the San Francisco Mobile 2.0 Meetup
February 5, 2009
Thursday, February 5, 2009

2. @al3x
@mzsanford
YOUR API TEAM
Confidence-inspiring!
Thursday, February 5, 2009

3. A BRIEF HISTORY
i. The incidental API.
ii.Documentation begets growth.
iii.The intentional API.
iv.The future!
Thursday, February 5, 2009

4. DEVELOPER SUPPORT
• More than just Alex & Matt.
• Better response time to issues, inquiries.
• More documentation, better documentation.
Thursday, February 5, 2009

5. COMMUNITY
• Primary goal: a better way to promote your apps.
• Organize and recommend apps to users.
• Pull developer resources into one place.
• When: Q2, if not sooner.
Thursday, February 5, 2009

6. OAUTH
•A standard for token-based authentication.
• Defeating the password anti-pattern.
• Code is live for our internal testing today.
• Sending out documentation tomorrow.
• Private beta starts within a week.
• Help us with the mobile user experience!
Thursday, February 5, 2009

7. THE FIREHOSE
•A way to move the stream of
all public tweets from our
servers to our partners.
• Previously XMPP, now HTTP.
• Private beta starting soon.
• No cost, just some paperwork.
Thursday, February 5, 2009

8. TWITTER API 2.0
• Unifies Search API and REST API.
• More RESTful: intuitive & consistent URLs and parameters.
• Versioning: http://api.twitter.com/1/method.xml
• New backend: better response time, less rate limiting.
Thursday, February 5, 2009

9. FACTS
• 3,400+
developers in our discussion/
announcement groups.
• 2,000+ registered applications.
• Way more apps out there - and yours!
• Japaneselanguage book out, English
language book coming soon.
Thursday, February 5, 2009

10. THANKS!
QUESTIONS?
More information about the Twitter API at
http://apiwiki.twitter.com/
Job opportunities at
http://twitter.com/jobs
Thursday, February 5, 2009