<?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: Is Apple making the same mistake all over again?</title>
	<atom:link href="http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/</link>
	<description>the department of planned spontaneity</description>
	<lastBuildDate>Tue, 11 May 2010 11:02:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/comment-page-1/#comment-903</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 28 Apr 2008 20:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.designvsdevelop.com/03/17/is-apple-making-the-same-mistake-all-over-again/#comment-903</guid>
		<description>@vinnie

#1 So would you spend your energy on developing a) a fee-based web application formatted for mobile devices where you would keep 100% of your revenue or b) a iPhone specific application where you keep 70%?

#2 I can see the argument for the distribution/transactions, but that usually isn&#039;t more than %5-10 of your costs (thinking of CC charges, bandwidth, and some sort of mechanism to make sure that people can&#039;t *easily* copy around your code). Committing the remaining 20-25% to Apple&#039;s marketing and sales efforts seems to be a bit princely to me, especially when that&#039;s something *you* should want control over (even if you hire someone to do it).</description>
		<content:encoded><![CDATA[<p>@vinnie</p>
<p>#1 So would you spend your energy on developing a) a fee-based web application formatted for mobile devices where you would keep 100% of your revenue or b) a iPhone specific application where you keep 70%?</p>
<p>#2 I can see the argument for the distribution/transactions, but that usually isn&#8217;t more than %5-10 of your costs (thinking of CC charges, bandwidth, and some sort of mechanism to make sure that people can&#8217;t *easily* copy around your code). Committing the remaining 20-25% to Apple&#8217;s marketing and sales efforts seems to be a bit princely to me, especially when that&#8217;s something *you* should want control over (even if you hire someone to do it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinnie</title>
		<link>http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/comment-page-1/#comment-902</link>
		<dc:creator>vinnie</dc:creator>
		<pubDate>Mon, 28 Apr 2008 18:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.designvsdevelop.com/03/17/is-apple-making-the-same-mistake-all-over-again/#comment-902</guid>
		<description>&quot;Why would an iPhone developer spend large resources on developing a rich iPhone app, only to hand 30% of their revenue to Apple?&quot;

1. 70% of something is still more than 100% of nothing, which is the current iphone developer landscape.

2. 30% doesn&#039;t seem too bad of a charge for most of your marketing, distribution, and sales channel. With the app store a lot of those three areas of your business are covered.</description>
		<content:encoded><![CDATA[<p>&#8220;Why would an iPhone developer spend large resources on developing a rich iPhone app, only to hand 30% of their revenue to Apple?&#8221;</p>
<p>1. 70% of something is still more than 100% of nothing, which is the current iphone developer landscape.</p>
<p>2. 30% doesn&#8217;t seem too bad of a charge for most of your marketing, distribution, and sales channel. With the app store a lot of those three areas of your business are covered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/comment-page-1/#comment-754</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 18 Mar 2008 01:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.designvsdevelop.com/03/17/is-apple-making-the-same-mistake-all-over-again/#comment-754</guid>
		<description>Yeah, the &quot;13 year old&quot; or &quot;quality control&quot; argument is still essentially Apple&#039;s elitism though. (Granted, a certain amount of this exclusiveness is what helps sell their products.)

The revenue cut is just a blatant money grab.</description>
		<content:encoded><![CDATA[<p>Yeah, the &#8220;13 year old&#8221; or &#8220;quality control&#8221; argument is still essentially Apple&#8217;s elitism though. (Granted, a certain amount of this exclusiveness is what helps sell their products.)</p>
<p>The revenue cut is just a blatant money grab.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://www.designvsdevelop.com/is-apple-making-the-same-mistake-all-over-again/comment-page-1/#comment-752</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Tue, 18 Mar 2008 01:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.designvsdevelop.com/03/17/is-apple-making-the-same-mistake-all-over-again/#comment-752</guid>
		<description>I&#039;ve heard some decent arguments for the entry fee - basically, with Apple allowing people to upload apps to their store, they want to keep the 13 year olds who aren&#039;t good programmers out (the argument was stated better than that).  Also, one could make a case for the developer split, but I&#039;m not as willing to buy that argument.  We&#039;ll see how it all plays out.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve heard some decent arguments for the entry fee &#8211; basically, with Apple allowing people to upload apps to their store, they want to keep the 13 year olds who aren&#8217;t good programmers out (the argument was stated better than that).  Also, one could make a case for the developer split, but I&#8217;m not as willing to buy that argument.  We&#8217;ll see how it all plays out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
