<?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: FAST RE-REVIEW: iMiles (for conference-start deadline)</title>
	<atom:link href="http://apprejections.com/index.php/post/113/feed" rel="self" type="application/rss+xml" />
	<link>http://apprejections.com/index.php/post/113</link>
	<description>Send app-rejection news to @redglassesapps on twitter</description>
	<lastBuildDate>Thu, 09 Sep 2010 11:23:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: AL Software</title>
		<link>http://apprejections.com/index.php/post/113/comment-page-1#comment-149</link>
		<dc:creator>AL Software</dc:creator>
		<pubDate>Sun, 06 Dec 2009 04:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://apprejections.com/?p=113#comment-149</guid>
		<description>Are developers expected to beg corporate VPs to fast track critical releases?  If that is not a glaring problem, I don&#039;t know what is...

The fact that they had to contact a corporate VP highlights the biggest problem with the App Store review process.  There is no official two-way communication channel between developers and Apple.  In a normal partnership (yes, technically developers and Apple are partners as they both mutually benefit from the App Store sales), there is a two-way dialog and partners *work together* to succeed.  Unfortunately, the relationship between Apple and developers is not a partnership at all.

The app submission process is essentially a one-way street: throw the app into a chute whose length can vary from 1 day to months and wait for the app to, hopefully, emerge at the other end.  There is no way for developers to engage with the review team before or during the review process, there is no way to prioritize updates (e.g. critical, major, minor, etc.), in practice there is very little hope of getting responses to inquiries after a rejection, there is no way for developers to know up front whether an app is likely to be rejected, etc.  In short, there is no dialog.  There is no cooperation.  It&#039;s &quot;throw the dice&quot; and see what comes up.  THAT is a major problem.</description>
		<content:encoded><![CDATA[<p>Are developers expected to beg corporate VPs to fast track critical releases?  If that is not a glaring problem, I don&#8217;t know what is&#8230;</p>
<p>The fact that they had to contact a corporate VP highlights the biggest problem with the App Store review process.  There is no official two-way communication channel between developers and Apple.  In a normal partnership (yes, technically developers and Apple are partners as they both mutually benefit from the App Store sales), there is a two-way dialog and partners *work together* to succeed.  Unfortunately, the relationship between Apple and developers is not a partnership at all.</p>
<p>The app submission process is essentially a one-way street: throw the app into a chute whose length can vary from 1 day to months and wait for the app to, hopefully, emerge at the other end.  There is no way for developers to engage with the review team before or during the review process, there is no way to prioritize updates (e.g. critical, major, minor, etc.), in practice there is very little hope of getting responses to inquiries after a rejection, there is no way for developers to know up front whether an app is likely to be rejected, etc.  In short, there is no dialog.  There is no cooperation.  It&#8217;s &#8220;throw the dice&#8221; and see what comes up.  THAT is a major problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
