<?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>Some Random Dude &#187; diversity</title>
	<atom:link href="http://www.somerandomdude.com/tag/diversity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.somerandomdude.com</link>
	<description>Some Random Dude is a blog by P.J. Onori that covers design &#38; technology in the broadest sense possible.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:37:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Twitter of 2006 Should Have a Talk With Twitter of 2011</title>
		<link>http://www.somerandomdude.com/2011/03/16/twitter-of-2006-should-have-a-talk-with-twitter-of-2011/</link>
		<comments>http://www.somerandomdude.com/2011/03/16/twitter-of-2006-should-have-a-talk-with-twitter-of-2011/#comments</comments>
		<pubDate>Wed, 16 Mar 2011 22:58:32 +0000</pubDate>
		<dc:creator>P.J. Onori</dc:creator>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[diversity]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://somerandomdude.com/?p=10170</guid>
		<description><![CDATA[The diversity inherent in public design/development was considered the strength of the Web 2.0 movement. In many ways, Twitter has become the behemoth it now is based on that very notion. In an odd turn, Twitter has decided to ask developers to stop making conventional Twitter apps. To put it lightly, there seems to be [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://somerandomdude.com/wp-content/uploads/tweet2.png" alt="Fail Whale" title="tweet2.png" border="0" width="560" height="330" /></p>
<p>The diversity inherent in public design/development was considered the strength of the Web 2.0 movement. In many ways, Twitter has become the behemoth it now is based on that very notion. In an odd turn, Twitter <a href='http://arstechnica.com/software/news/2011/03/twitter-tells-third-party-devs-to-stop-making-twitter-client-apps.ars'>has decided to ask developers to stop making conventional Twitter apps.</a>  To put it lightly, there seems to be a lack of historical perspective in this change in opinion. Perhaps the hardest part for myself to swallow is the fact that Twitter&#8217;s official client was not the product of an internal design team, but simply a revised version of an <a href='http://gigaom.com/2010/04/09/twitter-buys-tweetie-adds-fuel-to-developer-fires/'>acquired third-party application</a>.<span id="more-10170"></span></p>
<p>Ryan Sarver from Twitter communicates the reasoning behind this move:</p>
<blockquote><p>&#8220;We need to move to a less fragmented world, where every user can experience Twitter in a consistent way. This is already happening organically&#8211;the number and market share of consumer client apps that are not owned or operated by Twitter has been shrinking&#8230; Developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no.&#8221;</p></blockquote>
<p>Twitter makes it clear in this decision that they consider themselves more adept at providing the best experience for the public. I find framing this decision as championing user experience both problematic and disingenuous. On the contrary, Twitter has not exactly been the public&#8217;s best friend lately when it comes to user experience (see <a href='http://techcrunch.com/2011/03/08/twitter-responds-to-backlash-dickbar-no-longer-covers-tweets/<br />
'>#dickbar</a>). Taking a step back and surveying recent events, this seems to be a grab for eyeballs to monetize their content through apps <em>they own</em>. Twitter is now at the point where it simply no longer <em>needs</em> third-party developers to help drive their product. In fact, it may be proving to be a hinderance financially. To me, this makes far more sense than the notion that these decisions are all under the auspices of a better user experience.</p>
<p>At the very least, Twitter is biting the hand that fed them when they were still scrawny and vulnerable. If my speculations are correct, well, then it is another animal all together. Either way, Twitter would be wise not to wield user experience as the argument for this case. Users are smart. Diversity is <em>far</em> more beneficial than detrimental. The good software products have always had the tendency rise to the top&mdash;they do not need Twitter, or anyone for that matter, to hold their hand and tell them what product is best for them.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somerandomdude.com/2011/03/16/twitter-of-2006-should-have-a-talk-with-twitter-of-2011/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc (Feed is rejected)
Page Caching using apc
Database Caching 1/9 queries in 0.004 seconds using apc
Object Caching 262/274 objects using apc

Served from: www.somerandomdude.com @ 2012-02-09 17:54:50 -->
