<?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: Dear Adobe &#8211; A Lesson On Lowering Transaction Costs</title>
	<atom:link href="http://www.brooksandrus.com/blog/2008/08/21/dear-adobe-a-lesson-on-lowering-transaction-costs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brooksandrus.com/blog/2008/08/21/dear-adobe-a-lesson-on-lowering-transaction-costs/</link>
	<description>This is the blog of Brooks Andrus. Here, at irregular intervals, you may find digital noise centered around the activities of an early 21st century technologist. I work for TechSmith Corporation, but this web space and the views found on it are entirely my own.</description>
	<lastBuildDate>Sat, 13 Mar 2010 10:07:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Dowdell</title>
		<link>http://www.brooksandrus.com/blog/2008/08/21/dear-adobe-a-lesson-on-lowering-transaction-costs/comment-page-1/#comment-48421</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Fri, 22 Aug 2008 18:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/?p=247#comment-48421</guid>
		<description>I saw the site a few days ago and was immediately struck by how easy it was to write, how impossible it was to harvest.

Even Twitter is simpler... I&#039;ve been using TweetScan, Summize and other engines to harvest miscellaneous stuff out there for a year. (And if you ever read raw input like that, your brain would melt too.)

Smarter is to just go adobe.com/go/wish and drop a note directly to a product team.

Am I missing a button somewhere? How can that site&#039;s design be used? 

jd/adobe</description>
		<content:encoded><![CDATA[<p>I saw the site a few days ago and was immediately struck by how easy it was to write, how impossible it was to harvest.</p>
<p>Even Twitter is simpler&#8230; I&#8217;ve been using TweetScan, Summize and other engines to harvest miscellaneous stuff out there for a year. (And if you ever read raw input like that, your brain would melt too.)</p>
<p>Smarter is to just go adobe.com/go/wish and drop a note directly to a product team.</p>
<p>Am I missing a button somewhere? How can that site&#8217;s design be used? </p>
<p>jd/adobe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex McCabe</title>
		<link>http://www.brooksandrus.com/blog/2008/08/21/dear-adobe-a-lesson-on-lowering-transaction-costs/comment-page-1/#comment-48416</link>
		<dc:creator>Alex McCabe</dc:creator>
		<pubDate>Fri, 22 Aug 2008 11:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/?p=247#comment-48416</guid>
		<description>I wonder if there isn&#039;t room for Adobe to create simpler applications that read/write to the same source format (say .fla for example) but where the focus is on &#039;easy-to-use&#039; rather than powerful.

I don&#039;t mean a cut down app, so much as one that has been designed with simplicity in mind. That way a user can get started easily, but dip-into/migrate-to the powerful app as the need arises. I wonder if that would be a better way to capture new users rather than presenting them with an unmanageable interface from the start.</description>
		<content:encoded><![CDATA[<p>I wonder if there isn&#8217;t room for Adobe to create simpler applications that read/write to the same source format (say .fla for example) but where the focus is on &#8216;easy-to-use&#8217; rather than powerful.</p>
<p>I don&#8217;t mean a cut down app, so much as one that has been designed with simplicity in mind. That way a user can get started easily, but dip-into/migrate-to the powerful app as the need arises. I wonder if that would be a better way to capture new users rather than presenting them with an unmanageable interface from the start.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
