<?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>integration &#8211; API UX</title>
	<atom:link href="/tag/integration/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Everything about API User Experience</description>
	<lastBuildDate>Wed, 25 Jun 2014 16:30:51 +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>Time To Leave Your Keys At Home Or Better Yet Trash Them Forever</title>
		<link>/2014/06/25/leave-keys-home/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=leave-keys-home</link>
					<comments>/2014/06/25/leave-keys-home/#respond</comments>
		
		<dc:creator><![CDATA[Andree Huk]]></dc:creator>
		<pubDate>Wed, 25 Jun 2014 16:30:27 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[CarPlay]]></category>
		<category><![CDATA[HomeKit]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[sensor]]></category>
		<category><![CDATA[TouchID]]></category>
		<guid isPermaLink="false">/?p=1033</guid>

					<description><![CDATA[This post originally appeared on Andree&#8217;s personal blog. You can follow him here @andreehuk. Apple&#8216;s design goal is to create holistic and consistent experiences. Apple focuses exclusively on devices and services that they can control. In fact, this control actually has likely increased as Walt Mossberg writes about WWDC 2014 on re/code. Customers are being enticed more and more to stay [&#8230;]]]></description>
		
					<wfw:commentRss>/2014/06/25/leave-keys-home/feed/</wfw:commentRss>
			<slash:comments>0</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>Is end-user API UX a Utopia?</title>
		<link>/2013/03/26/end-user-api-ux-utopia/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=end-user-api-ux-utopia</link>
					<comments>/2013/03/26/end-user-api-ux-utopia/#comments</comments>
		
		<dc:creator><![CDATA[Jason Rados]]></dc:creator>
		<pubDate>Tue, 26 Mar 2013 17:00:58 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[end-user]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[tool]]></category>
		<category><![CDATA[troubleshoot]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[utopia]]></category>
		<category><![CDATA[UX]]></category>
		<guid isPermaLink="false">/?p=155</guid>

					<description><![CDATA[I have been working as a User Experience designer at CloudWork for the past 6 months and I&#8217;ve faced many challenges and opportunities while building an easy to use product that automates business processes and synchronizes cloud-based applications. The UI and UX of the application was very easy to create compared to the actual UX of [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/03/26/end-user-api-ux-utopia/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
