<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:www.readwriteweb.com,2011:/1/tag:www.readwriteweb.com,2009://1.14081-</id>
  <updated>2011-08-16T17:39:38Z</updated>
  <title>Comments for New Google Code Labs Clarifies Commitments to Developers</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.35-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14081</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=14081" title="New Google Code Labs Clarifies Commitments to Developers" />
    <published>2009-03-03T20:34:16Z</published>
    <updated>2009-03-03T21:55:59Z</updated>
    <title>New Google Code Labs Clarifies Commitments to Developers</title>
    <summary>Google announced today the launch of a new site, Google Code Labs, where developers can find links to all the major code projects that Google staff is working on. It&apos;s a central place to find APIs that 3rd parties can build off of and it includes a clarification of what projects Google has made a...</summary>
    <author>
      <name>Marshall Kirkpatrick</name>
      <uri>http://www.readwriteweb.com</uri>
    </author>
    
    <category term="Data Services" />
    
    <category term="NYT" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="googlecodelabslogo.jpg" src="http://www.readwriteweb.com/images/googlecodelabslogo.jpg" width="150" height="61">Google <a href="http://google-code-updates.blogspot.com/2009/03/introducing-labs-for-google-code.html">announced today</a> the launch of a new site, <a href="http://code.google.com/labs/">Google Code Labs</a>, where developers can find links to all the major code projects that Google staff is working on.  It's a central place to find APIs that 3rd parties can build off of and it includes a clarification of what projects Google has made a long term commitment to and what they have not.  We were a little surprised to see what the company considers "graduated" from Labs and what's still there.</p>

<p>Perhaps nothing like this should be a surprise coming from a company that built the leading webmail product online and still calls it Beta five years later.  </p>]]>
      <![CDATA[<p>By clarifying what's still in Labs and what's not, though, Google may enable other companies to know what they can depend on for building into products and what they might want to be cautious with.  The <a href="http://code.google.com/labs/">Code Lab</a> is not to be confused with the older and more general purpose <a href="http://labs.google.com/">Google Labs</a>.</p>

<p>Who's worn the virtual cap and gown already?  Twenty seven projects are listed as graduates, including the <a href="http://code.google.com/apis/youtube/">YouTube APIs</a>, <a href="http://code.google.com/apis/maps/">Maps APIs</a> and (thank goodness) <a href="http://code.google.com/apis/contacts/">Contacts API</a>.  We've been wondering why more developers aren't using the Contacts API but instead keep asking us for our precious Google passwords.  It's been <a href="http://www.readwriteweb.com/archives/google_releases_contacts_api.php">out for a whole year now</a>.  Now there can be no excuse!  The Contacts API is real, it's solid and Google is committed to supporting it.</p>

<p>Surprises among the 18 projects still deemed too green for prime time?  <a href="http://code.google.com/apis/gears/">Gears</a>, <a href="http://code.google.com/apis/finance/">Finance Data APIs</a>, <a href="http://code.google.com/apis/socialgraph/">Social Graph API</a> and the <a href="http://code.google.com/apis/feedburner/">Feedburner APIs</a>.  </p>

<p>Google APIs are an incredible resource and today's announcement should further their adoption.  We'll be monitoring the Code Labs page for the experimental availability of the inevitable Google Brain Implant API, but until that day comes we feel almost unconditionally excited about the code projects the Google teams are working on.</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14081-comment:128650</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14081" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php#c128650" />
    <title>Comment from Steve Webster on 2009-03-03</title>
    <author>
        <name>Steve Webster</name>
        <uri>http://dynamicflash.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://dynamicflash.com">
        <![CDATA[<p>Not to nitpick (well, okay, I am) but GMail is far from 'the leading webmail product. In fact, it's a distant third behind Yahoo! Mail and Hotmail / Live Mail.</p>

<p>See <a href="http://www.labnol.org/internet/email/market-share-of-web-email-services/5322/" rel="nofollow">http://www.labnol.org/internet/email/market-share-of-web-email-services/5322/</a><br />
</p>]]>
    </content>
    <published>2009-03-03T23:30:55Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14081-comment:128641</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14081" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/new_google_code_labs_clarifies_commitments_to_deve.php#c128641" />
    <title>Comment from Troy Malone on 2009-03-03</title>
    <author>
        <name>Troy Malone</name>
        <uri>http://www.pelotonics.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.pelotonics.com">
        <![CDATA[<p>Thanks for your coverage of this Marshall. We are in the tornado right now finishing up our integration with Google Docs. In doing this integration, we have found a few bugs in the Google API and now have to try and push the remedies along on their side. It is nice to know that we are using an API that is supported into the future. (we knew that before this post; I assure you!)</p>

<p>Integrations are great and add a ton of value to applications, but they do expose a company to API changes and uncertain support. It is good to see that Google is committed to this and that they are making it more clear for all of us!</p>

<p>Troy Malone<br />
Pelotonics</p>]]>
    </content>
    <published>2009-03-03T21:16:07Z</published>
  </entry>

</feed>
