<?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:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: App Store Roundtable: Transparency and the Approval System</title>
	<atom:link href="http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/</link>
	<description></description>
	<lastBuildDate>Sat, 26 May 2012 14:43:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Cryptopur</title>
		<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/#comment-344591</link>
		<dc:creator><![CDATA[Cryptopur]]></dc:creator>
		<pubDate>Wed, 03 Jun 2009 19:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=22580#comment-344591</guid>
		<description><![CDATA[I feel somewhere in the middle of Gazoobee and Msr. Gibson. We&#039;ve dealt with two rejections since we started. One of them was totally fair - they found a bug that e had missed and frankly I was glad that Apple caught it instead of our customers. But the other was so random and indecipherable we basically reworded our description text just a little and resubmitted to get approved. 

It&#039;s that second experience where even a little window to say &quot;What are you saying here?&quot; would have been SOOO valuable. It&#039;s also a very strange situation where developers are asked to commit significant time and money to a project before there is any ability to see the project approved or rejected. 

That&#039;s where a little give and take from Apple would make the system better for everybody, including Apple. As it is all developers are basically forced into a kind of &#039;throw everything up and see what sticks&#039; situation which only means Apple has a lot more apps to review than they really want and the app store omits apps that would be good, and includes apps that are just chaff.]]></description>
		<content:encoded><![CDATA[<p>I feel somewhere in the middle of Gazoobee and Msr. Gibson. We&#8217;ve dealt with two rejections since we started. One of them was totally fair &#8211; they found a bug that e had missed and frankly I was glad that Apple caught it instead of our customers. But the other was so random and indecipherable we basically reworded our description text just a little and resubmitted to get approved. </p>
<p>It&#8217;s that second experience where even a little window to say &#8220;What are you saying here?&#8221; would have been SOOO valuable. It&#8217;s also a very strange situation where developers are asked to commit significant time and money to a project before there is any ability to see the project approved or rejected. </p>
<p>That&#8217;s where a little give and take from Apple would make the system better for everybody, including Apple. As it is all developers are basically forced into a kind of &#8216;throw everything up and see what sticks&#8217; situation which only means Apple has a lot more apps to review than they really want and the app store omits apps that would be good, and includes apps that are just chaff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jakeadelphia &#187; Prototype (part 3)</title>
		<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/#comment-344590</link>
		<dc:creator><![CDATA[jakeadelphia &#187; Prototype (part 3)]]></dc:creator>
		<pubDate>Wed, 20 May 2009 20:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=22580#comment-344590</guid>
		<description><![CDATA[[...] approval process and then either unceremoniously submitted or denied with very little reasoning.  See here. The issue is one of transparency which is something that Apple has, for better or worse, been [...]]]></description>
		<content:encoded><![CDATA[<p>[...] approval process and then either unceremoniously submitted or denied with very little reasoning.  See here. The issue is one of transparency which is something that Apple has, for better or worse, been [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Gibson</title>
		<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/#comment-344589</link>
		<dc:creator><![CDATA[John Gibson]]></dc:creator>
		<pubDate>Thu, 07 May 2009 11:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=22580#comment-344589</guid>
		<description><![CDATA[Gazoobee,

It is not a situation where perception does not equate with reality.  I believe you are correct about the number of submissions and the difficulty that causes which is all the more reason to implement some kind of status update system.

The biggest problem with the App Store process is the terrible inconsistency in what constitutes cause for rejection.  I have no idea what the process is inside of Apple w/the process but the logical assumption must be that there is a complete lack of set guidelines as to what triggers a rejection.  And that is a huge problem where perception doesn&#039;t do reality justice.  It shouldn&#039;t be a crapshoot whether or not an app gets approval.]]></description>
		<content:encoded><![CDATA[<p>Gazoobee,</p>
<p>It is not a situation where perception does not equate with reality.  I believe you are correct about the number of submissions and the difficulty that causes which is all the more reason to implement some kind of status update system.</p>
<p>The biggest problem with the App Store process is the terrible inconsistency in what constitutes cause for rejection.  I have no idea what the process is inside of Apple w/the process but the logical assumption must be that there is a complete lack of set guidelines as to what triggers a rejection.  And that is a huge problem where perception doesn&#8217;t do reality justice.  It shouldn&#8217;t be a crapshoot whether or not an app gets approval.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gazoobee</title>
		<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/#comment-344588</link>
		<dc:creator><![CDATA[Gazoobee]]></dc:creator>
		<pubDate>Wed, 06 May 2009 21:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=22580#comment-344588</guid>
		<description><![CDATA[What all these articles that bash Apple over the app store fail to ever talk about (and this one is the same), is the sheer volume of the submissions and the relative newness of the entire operation.  

The app store hasn&#039;t even been around for very long at all and I happen to know they get a &quot;stupid ridiculous&quot; volume of submissions even if you don&#039;t count the upgrades and new versions or things.  What do people expect?  

Sure, things like Duck Hunt could have been avoided if there was one single experienced software expert looking at each submission, but that&#039;s just not possible folks.  The kinds of people (developers) who could easily catch these glitches as they happen are not interested in working for basic wages looking at tens of thousands of dull, technical submissions to the app store.  It&#039;s not possible for Steve to check every one and I don&#039;t see why no one ever seems to realise that.  

A bunch of people work really hard in boring conditions trying to figure out if the apps should be accepted or not.  They aren&#039;t developers, and they have a printed book of instructions and guidelines to work from.  They have to rely on people reporting these kind of things to them to a degree and while that has worked rather well for them, it&#039;s portrayed in the media and on sites like this as &quot;failure&quot; on Apple&#039;s part instead of what it really is which is Apple responding to complaints rather effectively and quickly.  

It&#039;s also the complaints that produce the perception that there is a &quot;problem&quot; when there really isn&#039;t so much.  If the developers weren&#039;t so hot to complain all the time and run Apple over the coals every time their update gets a rejection letter, half the problems would disappear.  

I&#039;m not suggesting that there aren&#039;t *any* problems, just that they are:

- mostly illusory
- to be expected
- shouldn&#039;t be whined about
- usually quickly fixed
- often have a very innocuous explanation

Most of the glitches in acceptance are worked out eventually and very very few apps]]></description>
		<content:encoded><![CDATA[<p>What all these articles that bash Apple over the app store fail to ever talk about (and this one is the same), is the sheer volume of the submissions and the relative newness of the entire operation.  </p>
<p>The app store hasn&#8217;t even been around for very long at all and I happen to know they get a &#8220;stupid ridiculous&#8221; volume of submissions even if you don&#8217;t count the upgrades and new versions or things.  What do people expect?  </p>
<p>Sure, things like Duck Hunt could have been avoided if there was one single experienced software expert looking at each submission, but that&#8217;s just not possible folks.  The kinds of people (developers) who could easily catch these glitches as they happen are not interested in working for basic wages looking at tens of thousands of dull, technical submissions to the app store.  It&#8217;s not possible for Steve to check every one and I don&#8217;t see why no one ever seems to realise that.  </p>
<p>A bunch of people work really hard in boring conditions trying to figure out if the apps should be accepted or not.  They aren&#8217;t developers, and they have a printed book of instructions and guidelines to work from.  They have to rely on people reporting these kind of things to them to a degree and while that has worked rather well for them, it&#8217;s portrayed in the media and on sites like this as &#8220;failure&#8221; on Apple&#8217;s part instead of what it really is which is Apple responding to complaints rather effectively and quickly.  </p>
<p>It&#8217;s also the complaints that produce the perception that there is a &#8220;problem&#8221; when there really isn&#8217;t so much.  If the developers weren&#8217;t so hot to complain all the time and run Apple over the coals every time their update gets a rejection letter, half the problems would disappear.  </p>
<p>I&#8217;m not suggesting that there aren&#8217;t *any* problems, just that they are:</p>
<p>- mostly illusory<br />
- to be expected<br />
- shouldn&#8217;t be whined about<br />
- usually quickly fixed<br />
- often have a very innocuous explanation</p>
<p>Most of the glitches in acceptance are worked out eventually and very very few apps</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Ellenich</title>
		<link>http://gigaom.com/apple/app-store-roundtable-transparency-and-the-approval-system/#comment-344587</link>
		<dc:creator><![CDATA[John Ellenich]]></dc:creator>
		<pubDate>Wed, 06 May 2009 18:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=22580#comment-344587</guid>
		<description><![CDATA[Luckily the approval process has been pretty smooth for us thus far– check out this little tid-bit of info about using the Application Loader before submitting– it helped us for Toast Timer...

http://bickbot.com/blog/use-application-loader-before-app-submission/]]></description>
		<content:encoded><![CDATA[<p>Luckily the approval process has been pretty smooth for us thus far– check out this little tid-bit of info about using the Application Loader before submitting– it helped us for Toast Timer&#8230;</p>
<p><a href="http://bickbot.com/blog/use-application-loader-before-app-submission/" rel="nofollow">http://bickbot.com/blog/use-application-loader-before-app-submission/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

