<?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: Facebook apps getting stuck in approval .. no more</title>
	<atom:link href="http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/</link>
	<description>bernie's small batches of software goodness</description>
	<lastBuildDate>Wed, 09 Sep 2009 04:48:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bernie Thompson</title>
		<link>http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/comment-page-1/#comment-21042</link>
		<dc:creator>Bernie Thompson</dc:creator>
		<pubDate>Tue, 13 Nov 2007 04:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/#comment-21042</guid>
		<description>I do think with Facebook, it&#039;s all about organic growth: friend profiles, news feed stories, and the like driving growth.  If you don&#039;t have that viral quality, driving growth with PR will be futile.

With a new app, though, I think you can&#039;t know if it will go viral unless it gets seen -- and that means getting it seeded into as wide a range of networks as possible (different geographies, age groups, colleges, etc.)

Getting it into the Facebook directory was step #1 to make it findable. Getting some reviews (honest, unsolicited, and hopefully positive) is Step #2. Step #3 is blogs and review sites outside of facebook.  Step  #4 is improving the app from all the feedback from 1-3 ... and back through the cycle again.

So basically, publish and pray isn&#039;t too far from the truth. ;)</description>
		<content:encoded><![CDATA[<p>I do think with Facebook, it&#8217;s all about organic growth: friend profiles, news feed stories, and the like driving growth.  If you don&#8217;t have that viral quality, driving growth with PR will be futile.</p>
<p>With a new app, though, I think you can&#8217;t know if it will go viral unless it gets seen &#8212; and that means getting it seeded into as wide a range of networks as possible (different geographies, age groups, colleges, etc.)</p>
<p>Getting it into the Facebook directory was step #1 to make it findable. Getting some reviews (honest, unsolicited, and hopefully positive) is Step #2. Step #3 is blogs and review sites outside of facebook.  Step  #4 is improving the app from all the feedback from 1-3 &#8230; and back through the cycle again.</p>
<p>So basically, publish and pray isn&#8217;t too far from the truth. <img src='http://leancode.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/comment-page-1/#comment-21041</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 13 Nov 2007 04:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://leancode.com/2007/11/12/facebook-apps-getting-stuck-in-approval-no-more/#comment-21041</guid>
		<description>Amazing what a half-million subscriber gorilla can do.

What&#039;s your publicity strategy for Karma club (other than organics)?  Come to think of it, what is the publicity strategy for any facebook app other than publish &amp; pray?</description>
		<content:encoded><![CDATA[<p>Amazing what a half-million subscriber gorilla can do.</p>
<p>What&#8217;s your publicity strategy for Karma club (other than organics)?  Come to think of it, what is the publicity strategy for any facebook app other than publish &amp; pray?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.658 seconds -->
