<?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"
	>
<channel>
	<title>Comments for FrameThink - Frameworks for Thinking People</title>
	<atom:link href="http://framethink.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://framethink.wordpress.com</link>
	<description>"I think (in frameworks) therefore I am."</description>
	<pubDate>Sat, 17 May 2008 21:19:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on About by yeeguy</title>
		<link>http://framethink.wordpress.com/about/#comment-39</link>
		<dc:creator>yeeguy</dc:creator>
		<pubDate>Wed, 02 Apr 2008 09:17:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-39</guid>
		<description>@Sarah -- yes, that's exactly right.  We really emphasized the use of data (both quantitative and qualitative) in guiding product decisions.  I think a core lesson about social apps and viral engineering is that there really *isn't* a single "silver bullet" metric that app publishers can/should focus on.  Instead, we tried to present virality as the product of many discrete variables that each need to be measured and collectively optimized.  A lot more info on this topic can be found here: http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/</description>
		<content:encoded><![CDATA[<p>@Sarah &#8212; yes, that&#8217;s exactly right.  We really emphasized the use of data (both quantitative and qualitative) in guiding product decisions.  I think a core lesson about social apps and viral engineering is that there really *isn&#8217;t* a single &#8220;silver bullet&#8221; metric that app publishers can/should focus on.  Instead, we tried to present virality as the product of many discrete variables that each need to be measured and collectively optimized.  A lot more info on this topic can be found here: <a href="http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/" rel="nofollow">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by -g &#187; Blog Archive &#187; FrameThink - Frameworks for Thinking People</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-38</link>
		<dc:creator>-g &#187; Blog Archive &#187; FrameThink - Frameworks for Thinking People</dc:creator>
		<pubDate>Wed, 02 Apr 2008 09:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-38</guid>
		<description>[...] particularly interesting post can be found here.  It goes through a very thorough explanation of four key dimensions to social application [...]</description>
		<content:encoded><![CDATA[<p>[...] particularly interesting post can be found here.  It goes through a very thorough explanation of four key dimensions to social application [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Sarah</title>
		<link>http://framethink.wordpress.com/about/#comment-33</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Mon, 17 Mar 2008 16:24:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-33</guid>
		<description>Hello,

I learned about your site after visiting the Stanford "Creating Apps For Facebook" group on Facebook. After learning more about the course and apps that the students developed, a central theme is clearly the use of metrics to identify and trigger iteration points. 

I'm curious as to what metrics proved to be the most valuable. Did the students identify any metrics that really provided them with great data for making specific changes to their applicaitons?

All the best,
Sarah</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I learned about your site after visiting the Stanford &#8220;Creating Apps For Facebook&#8221; group on Facebook. After learning more about the course and apps that the students developed, a central theme is clearly the use of metrics to identify and trigger iteration points. </p>
<p>I&#8217;m curious as to what metrics proved to be the most valuable. Did the students identify any metrics that really provided them with great data for making specific changes to their applicaitons?</p>
<p>All the best,<br />
Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by yeeguy</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-32</link>
		<dc:creator>yeeguy</dc:creator>
		<pubDate>Thu, 13 Mar 2008 22:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-32</guid>
		<description>@Jim -- yeah, a lot of app developers and bloggers have noted a slow down in viral growth rates recently.  The leading explanation is "app fatigue".  Facebook itself has been following the lead of user groups who have demanded that the practice of "forced invites" be put to an end.  And Facebook have even further tightened the screws on viral app growth by putting dynamic limits on the daily # of invites an app can send per user.

I think the current best practice is to use incentives to elicit more invites.  E.g., "send 5 more invites to unlock the ultra-cool whatchamacallit".  As you noted, this technique definitely has its limits and it places the ball squarely in the app publisher's court to create compelling functionality and/or content in order to drive continued app activity and invitations.</description>
		<content:encoded><![CDATA[<p>@Jim &#8212; yeah, a lot of app developers and bloggers have noted a slow down in viral growth rates recently.  The leading explanation is &#8220;app fatigue&#8221;.  Facebook itself has been following the lead of user groups who have demanded that the practice of &#8220;forced invites&#8221; be put to an end.  And Facebook have even further tightened the screws on viral app growth by putting dynamic limits on the daily # of invites an app can send per user.</p>
<p>I think the current best practice is to use incentives to elicit more invites.  E.g., &#8220;send 5 more invites to unlock the ultra-cool whatchamacallit&#8221;.  As you noted, this technique definitely has its limits and it places the ball squarely in the app publisher&#8217;s court to create compelling functionality and/or content in order to drive continued app activity and invitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by Jim Wolff</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-31</link>
		<dc:creator>Jim Wolff</dc:creator>
		<pubDate>Thu, 13 Mar 2008 12:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-31</guid>
		<description>Nice post - but do you think there'll come a point when  people develop resistance to the viral propagation suggestions you've made? I'm already beginning to notice a serious resistance to the invite-for-invites-sake features of apps - especially more 'functional' ones.

Tho as an app developer who can only manage a couple of thousand installs, I can't say i've got any better ideas :)</description>
		<content:encoded><![CDATA[<p>Nice post - but do you think there&#8217;ll come a point when  people develop resistance to the viral propagation suggestions you&#8217;ve made? I&#8217;m already beginning to notice a serious resistance to the invite-for-invites-sake features of apps - especially more &#8216;functional&#8217; ones.</p>
<p>Tho as an app developer who can only manage a couple of thousand installs, I can&#8217;t say i&#8217;ve got any better ideas <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by How Virality Works &#124; Prateek Dayal</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-27</link>
		<dc:creator>How Virality Works &#124; Prateek Dayal</dc:creator>
		<pubDate>Sat, 01 Mar 2008 15:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-27</guid>
		<description>[...] The Four Viral App Objectives (a.k.a., “Social network application virality 101″) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Four Viral App Objectives (a.k.a., “Social network application virality 101″) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by Marc Burch</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-26</link>
		<dc:creator>Marc Burch</dc:creator>
		<pubDate>Sun, 17 Feb 2008 00:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-26</guid>
		<description>Great post on the four viral app.</description>
		<content:encoded><![CDATA[<p>Great post on the four viral app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by yeeguy</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-22</link>
		<dc:creator>yeeguy</dc:creator>
		<pubDate>Fri, 08 Feb 2008 16:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-22</guid>
		<description>@Mike -- ah, thanks for bringing up the issue of time period.

I was actually thinking of K-factor as a "lifetime" measurement.  E.g., if you wait until a viral host either goes inactive or uninstalls an app, then measure how many new infections that host started during their "viral lifetime", then that's K.  

But, you're absolutely right -- you could measure K for shorter timespans and that would yield measurements like "monthly K" or "daily K".  (Starts to sound like a breakfast cereal.  Or maybe I'm just hungry.  ;-)

One drawback -- those types of time-based measurements will generally yield an inflated K-factor (because the original viral host will usually still be included in the active infected population).   So, if getting a short-timespan measurement is important, then app developers can try artificially capping the measured "lifetime" of their active viral hosts.  E.g., some techniques could include:
  * only consider a viral host to be active for the first M days after app install
  * only consider a viral host to be active during their first N visits to the app
  * only consider a viral host to be active for X invitation loops

With those type of capping techniques, you can very tightly delimit the viral loop time period to days, sometimes hours, and get a quick read on virality.  The obvious caveat: this will produce an artificially depressed K-factor measurement and the degree of impact will depend on how good the app is at driving repeat visits and continuous invitations.</description>
		<content:encoded><![CDATA[<p>@Mike &#8212; ah, thanks for bringing up the issue of time period.</p>
<p>I was actually thinking of K-factor as a &#8220;lifetime&#8221; measurement.  E.g., if you wait until a viral host either goes inactive or uninstalls an app, then measure how many new infections that host started during their &#8220;viral lifetime&#8221;, then that&#8217;s K.  </p>
<p>But, you&#8217;re absolutely right &#8212; you could measure K for shorter timespans and that would yield measurements like &#8220;monthly K&#8221; or &#8220;daily K&#8221;.  (Starts to sound like a breakfast cereal.  Or maybe I&#8217;m just hungry. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>One drawback &#8212; those types of time-based measurements will generally yield an inflated K-factor (because the original viral host will usually still be included in the active infected population).   So, if getting a short-timespan measurement is important, then app developers can try artificially capping the measured &#8220;lifetime&#8221; of their active viral hosts.  E.g., some techniques could include:<br />
  * only consider a viral host to be active for the first M days after app install<br />
  * only consider a viral host to be active during their first N visits to the app<br />
  * only consider a viral host to be active for X invitation loops</p>
<p>With those type of capping techniques, you can very tightly delimit the viral loop time period to days, sometimes hours, and get a quick read on virality.  The obvious caveat: this will produce an artificially depressed K-factor measurement and the degree of impact will depend on how good the app is at driving repeat visits and continuous invitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by Michael Weiksner</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-21</link>
		<dc:creator>Michael Weiksner</dc:creator>
		<pubDate>Fri, 08 Feb 2008 16:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-21</guid>
		<description>Yee,

Nice post.  Missing one factor: time period.  It is important that to minimize the time period over which the viral loop occurs.  It's the denominator to a fraction where you have correctly specified the numerator.

Cheers, and thanks for the post.

 - Mike</description>
		<content:encoded><![CDATA[<p>Yee,</p>
<p>Nice post.  Missing one factor: time period.  It is important that to minimize the time period over which the viral loop occurs.  It&#8217;s the denominator to a fraction where you have correctly specified the numerator.</p>
<p>Cheers, and thanks for the post.</p>
<p> - Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Four Viral App Objectives (a.k.a., &#8220;Social network application virality 101&#8243;) by links for 2008-02-08 at DeStructUred Blog</title>
		<link>http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-20</link>
		<dc:creator>links for 2008-02-08 at DeStructUred Blog</dc:creator>
		<pubDate>Fri, 08 Feb 2008 02:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://framethink.wordpress.com/2008/01/15/the-four-viral-app-objectives-aka-social-network-application-virality-101/#comment-20</guid>
		<description>[...] The Four Viral App Objectives (a.k.a., “Social network application virality 101″) « FrameThink ... (tags: viral facebook socialnetworks social apps metrics internet development) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Four Viral App Objectives (a.k.a., “Social network application virality 101″) « FrameThink &#8230; (tags: viral facebook socialnetworks social apps metrics internet development) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
