The main site already uses the API in some places. Our
revised mobile site is built entirely on the API, and our Facebook
application has been built off our API for some time.

Dogfooding! We support it.

On Tue, Sep 15, 2009 at 14:08, Jim Renkel <> wrote:
> I emphatically second and support the idea of having to use
> the API.
> We had similar quality problems at a place I formerly worked, and they
> were solved, completely, when such a policy was instituted.
> Yeah, it puts pressure on the API team and may inconvenience the UI
> team, or whatever you call them, but in the long run it will be worth
> it.
> Side effects that we saw were a simpler, cleaner, more consistent
> architecture for the whole system, and lower total costs to develop and
> maintain the system.
> Bite the bullet and do it now. The longer you wait, the more difficult
> and expensive it will be.
> Jim Renkel
> -----Original Message-----
> From:
> [] On Behalf Of Scott
> Haneda
> Sent: Tuesday, September 15, 2009 15:55
> To:
> Subject: [twitter-dev] Re: Comments for the group and Twitter staff
> Probably too late for this, but perhaps moving forward, it could be
> done...
> should move to using their own API.  The tools they use to
> power their own site should be the same tools we use and rely on.
> In all reality, this seems a simpler approach, rather than pushing out
> code for their stuff, and then essentially backporting that to an API,
> just work on making the API, and then integrate that into the
> site.
> As far as I can tell, this would solve pretty much every problem the
> API has, as there can not be a case where twitter is down, but the API
> is up, or the API is down, and twitter is up.
> Twitter should be eating their own dog food :)
> --
> Scott * If you contact me off list replace talklists@ with scott@ *

Alex Payne - Platform Lead, Twitter, Inc.

Reply via email to