<?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: Monetization Watch: QikCom</title>
	<atom:link href="http://pistachioconsulting.com/monetization-watch-qikcom/feed/" rel="self" type="application/rss+xml" />
	<link>http://pistachioconsulting.com/monetization-watch-qikcom/</link>
	<description>Micro sharing. Macro results.</description>
	<lastBuildDate>Fri, 30 Jul 2010 07:40:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: The Secret to Twitter Monetization Is&#8230; &#124; Open Mode</title>
		<link>http://pistachioconsulting.com/monetization-watch-qikcom/comment-page-1/#comment-18536</link>
		<dc:creator>The Secret to Twitter Monetization Is&#8230; &#124; Open Mode</dc:creator>
		<pubDate>Tue, 16 Dec 2008 17:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://pistachioconsulting.com/?p=1713#comment-18536</guid>
		<description>[...] Monetization Watch: QikCom [...]</description>
		<content:encoded><![CDATA[<p>[...] Monetization Watch: QikCom [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil</title>
		<link>http://pistachioconsulting.com/monetization-watch-qikcom/comment-page-1/#comment-17636</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Mon, 08 Dec 2008 08:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://pistachioconsulting.com/?p=1713#comment-17636</guid>
		<description>Johnathon, so that&#039;s from the perspective of the app authors (?). I think I was coming from the perspective of the end user of the app/tab - obviously both POVs are relevant - but I was wondering how useful I would find applications that have to work within the confines of the QuickCom interface, versus those that can live on their own domain name with a fully-fledged interface. The iPhone differentiates because of the mobile &amp; touch screen aspect, QuickCom &amp; app/tabs have to fight within the confines of the Web browser in general. It&#039;ll be very interesting to hear more on the developments at QuickCom via Pistachio (please try and tease out more info on revenue!).</description>
		<content:encoded><![CDATA[<p>Johnathon, so that&#8217;s from the perspective of the app authors (?). I think I was coming from the perspective of the end user of the app/tab &#8211; obviously both POVs are relevant &#8211; but I was wondering how useful I would find applications that have to work within the confines of the QuickCom interface, versus those that can live on their own domain name with a fully-fledged interface. The iPhone differentiates because of the mobile &amp; touch screen aspect, QuickCom &amp; app/tabs have to fight within the confines of the Web browser in general. It&#8217;ll be very interesting to hear more on the developments at QuickCom via Pistachio (please try and tease out more info on revenue!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Kash</title>
		<link>http://pistachioconsulting.com/monetization-watch-qikcom/comment-page-1/#comment-17607</link>
		<dc:creator>Jonathan Kash</dc:creator>
		<pubDate>Mon, 08 Dec 2008 01:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://pistachioconsulting.com/?p=1713#comment-17607</guid>
		<description>Great question, Neil. Ideally, apps will be portable and could be repurposed for any environment. 

Apps/tabs present a more manageable level of risk for organizations. I use Basecamp and think it&#039;s a great app; the investment required to present an alternative to the marketplace would be substantial. Costs would include development time, hosting, infrastructure, marketing and other overhead. An app could be produced for far less and would provide exposure needed to fund future growth.</description>
		<content:encoded><![CDATA[<p>Great question, Neil. Ideally, apps will be portable and could be repurposed for any environment. </p>
<p>Apps/tabs present a more manageable level of risk for organizations. I use Basecamp and think it&#8217;s a great app; the investment required to present an alternative to the marketplace would be substantial. Costs would include development time, hosting, infrastructure, marketing and other overhead. An app could be produced for far less and would provide exposure needed to fund future growth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil</title>
		<link>http://pistachioconsulting.com/monetization-watch-qikcom/comment-page-1/#comment-17281</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Thu, 04 Dec 2008 21:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://pistachioconsulting.com/?p=1713#comment-17281</guid>
		<description>It&#039;s great to see a startup trying a different (albeit, established on iPhone) route to revenue. Johnathon, how do you think Apps/Tabs will fair against standalone apps that don&#039;t have to sit within the confines of a QuickCom tab? Having a separate tab within an interface (on which you&#039;re already browsing) is often less convenient than a bookmark for a service like Basecamp, if the core features (in this case, status updates) aren&#039;t fully integrated with the functionality extensions provided by the tab.</description>
		<content:encoded><![CDATA[<p>It&#8217;s great to see a startup trying a different (albeit, established on iPhone) route to revenue. Johnathon, how do you think Apps/Tabs will fair against standalone apps that don&#8217;t have to sit within the confines of a QuickCom tab? Having a separate tab within an interface (on which you&#8217;re already browsing) is often less convenient than a bookmark for a service like Basecamp, if the core features (in this case, status updates) aren&#8217;t fully integrated with the functionality extensions provided by the tab.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
