<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>developer &#8211; API UX</title>
	<atom:link href="/tag/developer/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Everything about API User Experience</description>
	<lastBuildDate>Mon, 10 Nov 2014 10:08:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.8.6</generator>
	<item>
		<title>Predictive APIs: Bringing Machine Learning to the Masses</title>
		<link>/2014/11/10/predictive-apis/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=predictive-apis</link>
					<comments>/2014/11/10/predictive-apis/#comments</comments>
		
		<dc:creator><![CDATA[Manfred Bortenschlager]]></dc:creator>
		<pubDate>Mon, 10 Nov 2014 10:08:37 +0000</pubDate>
				<category><![CDATA[Conference]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[3scale]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[APItools]]></category>
		<category><![CDATA[Barcelona]]></category>
		<category><![CDATA[Bicing]]></category>
		<category><![CDATA[BigML]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[PAPIs]]></category>
		<category><![CDATA[predictive]]></category>
		<category><![CDATA[tools]]></category>
		<guid isPermaLink="false">/?p=1151</guid>

					<description><![CDATA[To help make Predictive APIs more mainstream and accessible, Louis Dorard is organizing the 1st International Conference on Predictive APIs and Apps (PAPIs) as general chair.]]></description>
		
					<wfw:commentRss>/2014/11/10/predictive-apis/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>API Strategy &#038; Practice Chicago</title>
		<link>/2014/09/04/apistrat-chicago/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=apistrat-chicago</link>
					<comments>/2014/09/04/apistrat-chicago/#respond</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Thu, 04 Sep 2014 20:19:34 +0000</pubDate>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Conference]]></category>
		<category><![CDATA[3scale]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[api evangelist]]></category>
		<category><![CDATA[APIStrat]]></category>
		<category><![CDATA[Chicago]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[hackathon]]></category>
		<guid isPermaLink="false">/?p=1111</guid>

					<description><![CDATA[The API Strategy &#038; Practice Conference (APIStrat) focuses on what works for API creators and consumers alike by bringing industry leaders together in one forum.]]></description>
		
					<wfw:commentRss>/2014/09/04/apistrat-chicago/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Nordic APIs conference wrap-up</title>
		<link>/2013/09/24/nordic-apis-wrap-up/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=nordic-apis-wrap-up</link>
					<comments>/2013/09/24/nordic-apis-wrap-up/#comments</comments>
		
		<dc:creator><![CDATA[Andreas Krohn]]></dc:creator>
		<pubDate>Tue, 24 Sep 2013 16:00:23 +0000</pubDate>
				<category><![CDATA[Conference]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[nordic]]></category>
		<category><![CDATA[presentation]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[speakers]]></category>
		<category><![CDATA[Stockholm]]></category>
		<category><![CDATA[Sweden]]></category>
		<category><![CDATA[wrap-up]]></category>
		<guid isPermaLink="false">/?p=669</guid>

					<description><![CDATA[The biggest Nordic APIs conference to date was held in Stockholm, Sweden 18-19 September, 2013. As one of the organizers I am proud to say everything went very well and that we did what we set out to do &#8211; which was to create a place for the API community in the Nordics to meet in person. [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/09/24/nordic-apis-wrap-up/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Tictail API launch focuses on UX</title>
		<link>/2013/09/19/tictail-api-launch-focuses-ux/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=tictail-api-launch-focuses-ux</link>
					<comments>/2013/09/19/tictail-api-launch-focuses-ux/#comments</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Thu, 19 Sep 2013 18:34:42 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[launch]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[portal]]></category>
		<category><![CDATA[standard]]></category>
		<category><![CDATA[Tictail]]></category>
		<category><![CDATA[UX]]></category>
		<guid isPermaLink="false">/?p=659</guid>

					<description><![CDATA[Tictail, a Swedish e-commerce platform that manages over 24,000 stores spread across 110 different countries, launched their API on September 16, 2013. Because Tictail&#8217;s main focus is simplicity of use, they decided to offer developers the same tools they use internally to build this new platform. According to Carl Waldekranz, Tictail CEO, they &#8220;want developers to [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/09/19/tictail-api-launch-focuses-ux/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>APIDays San Francisco</title>
		<link>/2013/06/24/apidays-san-francisco/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=apidays-san-francisco</link>
					<comments>/2013/06/24/apidays-san-francisco/#comments</comments>
		
		<dc:creator><![CDATA[Michael Pratt]]></dc:creator>
		<pubDate>Mon, 24 Jun 2013 10:49:55 +0000</pubDate>
				<category><![CDATA[Conference]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[APIUX]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[developer]]></category>
		<guid isPermaLink="false">/?p=497</guid>

					<description><![CDATA[At the conclusion of the first API Days San Francisco, one thing is clear above all else: APIs are in. Huge growth in the startup space developing APIs and major acquisitions amongst the larger companies are a great indicator of a burgeoning API ecosystem. Despite a wide variety of opinions and philosophies in the speaking [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/06/24/apidays-san-francisco/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>API Hierarchy of Needs</title>
		<link>/2013/05/29/api-hierarchy-needs/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=api-hierarchy-needs</link>
					<comments>/2013/05/29/api-hierarchy-needs/#comments</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Wed, 29 May 2013 21:07:30 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[creativity]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[Maslow]]></category>
		<category><![CDATA[need]]></category>
		<category><![CDATA[proficiency]]></category>
		<category><![CDATA[pyramid]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[usability]]></category>
		<guid isPermaLink="false">/?p=454</guid>

					<description><![CDATA[The hierarchy of needs is a pyramid divided into five different layers that represent different characteristics that you should consider when launching and maintaining an API.]]></description>
		
					<wfw:commentRss>/2013/05/29/api-hierarchy-needs/feed/</wfw:commentRss>
			<slash:comments>14</slash:comments>
		
		
			</item>
		<item>
		<title>Do you really need API Versioning?</title>
		<link>/2013/05/14/api-versioning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=api-versioning</link>
					<comments>/2013/05/14/api-versioning/#comments</comments>
		
		<dc:creator><![CDATA[Andreas Krohn]]></dc:creator>
		<pubDate>Tue, 14 May 2013 16:00:03 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[life cycle]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[version]]></category>
		<category><![CDATA[versioning]]></category>
		<guid isPermaLink="false">/?p=379</guid>

					<description><![CDATA[The only thing that we know for certain about the future is that things will change, and that is especially true in our industry. If your APIs are successful they will be used in ways you never had foreseen and the data you deliver will be combined with other data in very surprising ways.]]></description>
		
					<wfw:commentRss>/2013/05/14/api-versioning/feed/</wfw:commentRss>
			<slash:comments>16</slash:comments>
		
		
			</item>
		<item>
		<title>2 steps to better API Error Codes</title>
		<link>/2013/03/28/2-steps-api-error-codes/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=2-steps-api-error-codes</link>
					<comments>/2013/03/28/2-steps-api-error-codes/#comments</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Thu, 28 Mar 2013 17:00:03 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[RFC 2616]]></category>
		<category><![CDATA[steps]]></category>
		<category><![CDATA[UX]]></category>
		<category><![CDATA[XML.protocol]]></category>
		<guid isPermaLink="false">/?p=171</guid>

					<description><![CDATA[One of the biggest difficulties developers can have when writing code that talks with an API is dealing with errors and exceptions, and translating those errors into something meaningful for their applications.]]></description>
		
					<wfw:commentRss>/2013/03/28/2-steps-api-error-codes/feed/</wfw:commentRss>
			<slash:comments>14</slash:comments>
		
		
			</item>
		<item>
		<title>Authentication: Don&#8217;t be Clever</title>
		<link>/2013/03/21/authentication-dont-be-clever/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=authentication-dont-be-clever</link>
					<comments>/2013/03/21/authentication-dont-be-clever/#comments</comments>
		
		<dc:creator><![CDATA[John Sheehan]]></dc:creator>
		<pubDate>Thu, 21 Mar 2013 17:00:00 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[credential]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[error message]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[REST]]></category>
		<guid isPermaLink="false">/?p=112</guid>

					<description><![CDATA[HTTP API authentication has evolved through many forms over the years. As so-called RESTful APIs gained popularity, a variety of methods sprung up: key passing, plain-old HTTP Basic Auth, OAuth 1.0, OAuth 1.0a, OAuth 2.0 (and it&#8217;s 40 revision) and some less-common custom schemes. With the OAuth 2.0 specification finalized, things are finally starting to [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/03/21/authentication-dont-be-clever/feed/</wfw:commentRss>
			<slash:comments>14</slash:comments>
		
		
			</item>
		<item>
		<title>What is API User Experience?</title>
		<link>/2013/03/19/what-is-api-user-experience/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=what-is-api-user-experience</link>
					<comments>/2013/03/19/what-is-api-user-experience/#respond</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Tue, 19 Mar 2013 17:00:51 +0000</pubDate>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[APIUX]]></category>
		<category><![CDATA[definition]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[ease of use]]></category>
		<category><![CDATA[efficiency]]></category>
		<category><![CDATA[emotion]]></category>
		<category><![CDATA[ISO 9241-210]]></category>
		<category><![CDATA[perception]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[service]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[utility]]></category>
		<category><![CDATA[UX]]></category>
		<guid isPermaLink="false">/?p=24</guid>

					<description><![CDATA[API User Experience, or API UX, is a person's perceptions of the utility, ease of use and efficiency of an application API that result from its direct or indirect use. API UX covers two major types of users: developers, who benefit from direct use of APIs and end-users, who use APIs indirectly through consumer applications.]]></description>
		
					<wfw:commentRss>/2013/03/19/what-is-api-user-experience/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
