<?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/"
			xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
		
	>
<channel>
	<title>Comments on: The problems with app-based billing for data</title>
	<atom:link href="http://research.gigaom.com/2012/02/the-problems-with-app-based-billing-for-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://research.gigaom.com/2012/02/the-problems-with-app-based-billing-for-data/</link>
	<description></description>
	<lastBuildDate>Thu, 05 Mar 2015 18:27:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1</generator>
	<item>
		<title>By: Colin Gibbs</title>
		<link>http://research.gigaom.com/2012/02/the-problems-with-app-based-billing-for-data/#comment-1549</link>
		<dc:creator><![CDATA[Colin Gibbs]]></dc:creator>
		<pubDate>Wed, 11 Apr 2012 03:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://pro.gigaom.com/?p=99613#comment-1549</guid>
		<description><![CDATA[Thanks for the comments, DS21.

I see your point that demand (based on use cases) could certainly impact consumers&#039; willingness to pay for access, but I think there are too many variables to actually build a billing model accordingly. For instance, I may not be willing to pay much to keep my kid occupied with Netflix on a Saturday morning, but perhaps I&#039;d pony up in a big way for the same app but for a different use -- when I&#039;m in my hotel room with rotten (and expensive) Wi-Fi, for instance. 

My point is that many (or maybe most) of us have varying demand for our apps based on fluid situations and use cases. So convincing us to pay monthly fees for preferred access through certain apps seems like a pretty tough sell. 

That said, I can see where situational-based pricing for access might be a part of a larger solution. But I think that scenario differs from straight app-based pricing.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comments, DS21.</p>
<p>I see your point that demand (based on use cases) could certainly impact consumers&#8217; willingness to pay for access, but I think there are too many variables to actually build a billing model accordingly. For instance, I may not be willing to pay much to keep my kid occupied with Netflix on a Saturday morning, but perhaps I&#8217;d pony up in a big way for the same app but for a different use &#8212; when I&#8217;m in my hotel room with rotten (and expensive) Wi-Fi, for instance. </p>
<p>My point is that many (or maybe most) of us have varying demand for our apps based on fluid situations and use cases. So convincing us to pay monthly fees for preferred access through certain apps seems like a pretty tough sell. </p>
<p>That said, I can see where situational-based pricing for access might be a part of a larger solution. But I think that scenario differs from straight app-based pricing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donsmith21</title>
		<link>http://research.gigaom.com/2012/02/the-problems-with-app-based-billing-for-data/#comment-1544</link>
		<dc:creator><![CDATA[donsmith21]]></dc:creator>
		<pubDate>Tue, 10 Apr 2012 01:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://pro.gigaom.com/?p=99613#comment-1544</guid>
		<description><![CDATA[It&#039;s tricky, but there is some validity to the argument. Most consumers believe that all data is created equal and we should be able to use it as we wish. Carriers would like to differentiate themselves and optimize their networks. Sure, putting up more towers and having &quot;fatter mobile pipes&quot; solves the problem, but that can&#039;t happen overnight and even if it could it&#039;s not always cost effective. Somehow there needs to be a compromise. Let&#039;s say two people are using the same device on the same network and their apps are asking for similar bandwidths. Consumer A needs to log into Skype for an important video conference call. Customer B has handed his kid his device to watch Netflix. Undoubtedly Customer A would be willing to pay a bit more for preference on the network. If the network provider allocates the same bandwidth for both, Customer A will be upset. If Customer A is given preference, chances are that Customer B won&#039;t care. Or, just maybe Customer B does not mind paying more so Sponge Bob is clearer for his kid.

But how is the carrier to know? Most consumers will likely be overwhelmed if we are presented with list of apps and are asked to allocate their bandwidth preference based on network congestion, time of day, usage etc. Tiered pricing needs to happen. One of the angles that might work is to have the app provider pay for the bandwidth preference. Netflix (Free App) or Netflix Plus (Pay $5 a month) so you get network preference.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s tricky, but there is some validity to the argument. Most consumers believe that all data is created equal and we should be able to use it as we wish. Carriers would like to differentiate themselves and optimize their networks. Sure, putting up more towers and having &#8220;fatter mobile pipes&#8221; solves the problem, but that can&#8217;t happen overnight and even if it could it&#8217;s not always cost effective. Somehow there needs to be a compromise. Let&#8217;s say two people are using the same device on the same network and their apps are asking for similar bandwidths. Consumer A needs to log into Skype for an important video conference call. Customer B has handed his kid his device to watch Netflix. Undoubtedly Customer A would be willing to pay a bit more for preference on the network. If the network provider allocates the same bandwidth for both, Customer A will be upset. If Customer A is given preference, chances are that Customer B won&#8217;t care. Or, just maybe Customer B does not mind paying more so Sponge Bob is clearer for his kid.</p>
<p>But how is the carrier to know? Most consumers will likely be overwhelmed if we are presented with list of apps and are asked to allocate their bandwidth preference based on network congestion, time of day, usage etc. Tiered pricing needs to happen. One of the angles that might work is to have the app provider pay for the bandwidth preference. Netflix (Free App) or Netflix Plus (Pay $5 a month) so you get network preference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
