<?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: Thoughts on The Future and Progress In Our Work</title>
	<atom:link href="http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/</link>
	<description>You dream it up, we code it to life.</description>
	<lastBuildDate>Sat, 13 Mar 2010 11:41:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The BraveNewCode Roadmap &#8249; BraveNewCode Inc.</title>
		<link>http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/comment-page-1/#comment-5016</link>
		<dc:creator>The BraveNewCode Roadmap &#8249; BraveNewCode Inc.</dc:creator>
		<pubDate>Sun, 24 Jan 2010 18:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=2228#comment-5016</guid>
		<description>[...] posted here a few times  in the past about the release of WPtouch 2.0, and each time we&#8217;ve done so we [...]</description>
		<content:encoded><![CDATA[<p>[...] posted here a few times  in the past about the release of WPtouch 2.0, and each time we&#8217;ve done so we [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paintings by Monkeys &#183; WPTouch</title>
		<link>http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/comment-page-1/#comment-4950</link>
		<dc:creator>Paintings by Monkeys &#183; WPTouch</dc:creator>
		<pubDate>Wed, 11 Nov 2009 20:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=2228#comment-4950</guid>
		<description>[...] I&#8217;ll be closely watching the new features WPTouch is working on and where they see the future of mobile web applications head.... [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ll be closely watching the new features WPtouch is working on and where they see the future of mobile web applications head&#8230;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/comment-page-1/#comment-4943</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Sat, 07 Nov 2009 22:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=2228#comment-4943</guid>
		<description>That sort of model really is not ideal, for a number of reasons. One of the more prominent ones is time- some features take hours, others minutes.  

We&#039;d rather build a model where support itself is a part of a paid account, and then the incentive is there on both sides to enhance and grow the plugin.</description>
		<content:encoded><![CDATA[<p>That sort of model really is not ideal, for a number of reasons. One of the more prominent ones is time- some features take hours, others minutes.  </p>
<p>We&#8217;d rather build a model where support itself is a part of a paid account, and then the incentive is there on both sides to enhance and grow the plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Lane</title>
		<link>http://www.bravenewcode.com/2009/11/thoughts-on-the-future-and-progress-in-our-work/comment-page-1/#comment-4940</link>
		<dc:creator>J Lane</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=2228#comment-4940</guid>
		<description>Love your plugins guys, and am very grateful.  It&#039;s obvious that you&#039;ve put a ton of work and a great attention to detail in building them.

Have you ever thought about explicitly offering a &quot;pay-for-feature/pay-for-fix&quot; for any naysayers you encounter?  So if somebody really is between a rock and a hard place, and needs something, then they can pay to have it done.  Basically the same thing as hiring you for custom work, it would be very narrowly focussed, probably very short term, and you could offer it at a fixed price.  Then it really turns into a case of &quot;put your money where your mouth is&quot;.</description>
		<content:encoded><![CDATA[<p>Love your plugins guys, and am very grateful.  It&#8217;s obvious that you&#8217;ve put a ton of work and a great attention to detail in building them.</p>
<p>Have you ever thought about explicitly offering a &#8220;pay-for-feature/pay-for-fix&#8221; for any naysayers you encounter?  So if somebody really is between a rock and a hard place, and needs something, then they can pay to have it done.  Basically the same thing as hiring you for custom work, it would be very narrowly focussed, probably very short term, and you could offer it at a fixed price.  Then it really turns into a case of &#8220;put your money where your mouth is&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
