<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The two types of APIs</title>
	<atom:link href="http://www.adamduvander.com/projects/the-two-types-of-apis/feed" rel="self" type="application/rss+xml" />
	<link>http://www.adamduvander.com/projects/the-two-types-of-apis</link>
	<description>Adam DuVander’s thoughts on keeping things simple.</description>
	<lastBuildDate>Mon, 09 Jan 2012 07:03:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Web Things Considered &#38;#187; Web APIs shifting</title>
		<link>http://www.adamduvander.com/projects/the-two-types-of-apis/comment-page-1#comment-585</link>
		<dc:creator>Web Things Considered &#38;#187; Web APIs shifting</dc:creator>
		<pubDate>Thu, 21 Dec 2006 06:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://adamduvander.com/projects/the-two-types-of-apis#comment-585</guid>
		<description>[...] We talked about APIs back at the September PDX Web Innovators meeting, and much of that was focused around building mashups off of these services. I think it will be a real bummer if this trend continues, and less mashup-friendly services are offered. I agree with Dare that a site would be stupid to restrict ways to add stuff to your site. But it also strikes me that controlling the data extraction type of API would be a first step towards limiting a site&#8217;s viral uptake (though I&#8217;m sure Google&#8217;s not to concerned with that). [...]</description>
		<content:encoded><![CDATA[<p>[...] We talked about APIs back at the September PDX Web Innovators meeting, and much of that was focused around building mashups off of these services. I think it will be a real bummer if this trend continues, and less mashup-friendly services are offered. I agree with Dare that a site would be stupid to restrict ways to add stuff to your site. But it also strikes me that controlling the data extraction type of API would be a first step towards limiting a site&#38;#8217;s viral uptake (though I&#38;#8217;m sure Google&#38;#8217;s not to concerned with that). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Things Considered &#38;#187; The results of having a successful API</title>
		<link>http://www.adamduvander.com/projects/the-two-types-of-apis/comment-page-1#comment-584</link>
		<dc:creator>Web Things Considered &#38;#187; The results of having a successful API</dc:creator>
		<pubDate>Wed, 20 Sep 2006 16:46:33 +0000</pubDate>
		<guid isPermaLink="false">http://adamduvander.com/projects/the-two-types-of-apis#comment-584</guid>
		<description>[...] APIs were the topic at our Septemeber Web Innobators meeting and Adam has some notes. On the topic of what companies get out of having an API, if it&#8217;s good enough, people will write books about it. We&#8217;ve seen it with the Google Hacks and Amazon Hacks books and now the trend continues with a line of Flickr books. I&#8217;d argue that this is a good sign that your service has arrived, helps to increase mindshare and gets more people using your service, which ultimately will increase the bottom line. But, again the key here is it has to be from a service that&#8217;s compelling enough. So, producing an API to your new web service is probably not important to get in the intial set of features. But, if your service starts to gain traction, you better be considering it. [...]</description>
		<content:encoded><![CDATA[<p>[...] APIs were the topic at our Septemeber Web Innobators meeting and Adam has some notes. On the topic of what companies get out of having an API, if it&#38;#8217;s good enough, people will write books about it. We&#38;#8217;ve seen it with the Google Hacks and Amazon Hacks books and now the trend continues with a line of Flickr books. I&#38;#8217;d argue that this is a good sign that your service has arrived, helps to increase mindshare and gets more people using your service, which ultimately will increase the bottom line. But, again the key here is it has to be from a service that&#38;#8217;s compelling enough. So, producing an API to your new web service is probably not important to get in the intial set of features. But, if your service starts to gain traction, you better be considering it. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

