App Store approvals: Still more transparency needed

Posted by Adam Wyss on Nov 16, 2009

closeThis post was published 5 years 7 days ago which may make its actuality or expire date not be valid anymore. This site is not responsible for any misunderstanding.

trillian-contactlist-not approved

There has been a lot of news during the past week about the App Store, and the approval process that comes along with it.  Apple clearly needs to work on this process and absolutely must be more transparent.  One thing that I’m not sure they understand is that they are impeding other companies such as Cerulean Studios from doing business entirely or severely hindering it. That being said, here’s a roundup of some of the more popular App Store horror stories over the past week or so:

1.  Facebook for iPhone developer Joe Hewitt has very publicly quit developing for the iPhone platform out of protest to Apple’s policies.   (TechCrunch)

2. Apple implements a new software tool for app approvals to check API usage.  Developers are only allowed to use documented API’s in their apps and Apple has a new toy to make sure developers are really playing by the rules. (Twitter via @Gruber)

3. Rogue Amoeba, the developers of AirFoil and AirFoil Speakers Touch for iPhone, have also decided to stop supporting the iPhone platform until things change.  Their big issue is that a bug fix update was held up for over 3 and a half months because of some API’s that their Mac app uses to send images of the computer and application to the iPhone app.  What it turned into is a trademark dispute and Rogue Amoeba decided just to back down and ship an update without the pictures in it.  This is ridiculous because the API’s are public, documented API’s on Snow Leopard and they had not violated any written iPhone SDK or any of Apple’s rules on 3rd parties using their trademarks.  If you look at any of the 3 following articles, head over to the last link at Daring Fireball first.  It gives a good 3rd party breakdown of the situation, and even dissects another blog’s response which actually defends Apple in this case. 
(Rogue Amoeba original post)
(Rogue Amoeba update post)
(Daring Fireball)

Cerulean Studios, developers of the ever popular Trillian IM client have developed an iPhone version their newest version, Trillian Astra.  This app was submitted on August 14, 2009.  As of this writing, it has been “In Review” for a whopping 94 days now!  In my opinion, this is freaking ridiculous!  As you can see, Apple really desperately needs help here.  While Cerulean Studios has not posted a blog update since the 60 day mark in the review process, I want to help get the word out on their iPhone app and help get the word out even more about how broken Apple’s review process is.  There are other (great) IM apps out there with push notifications and Trillian Astra is just another one to fall into that category, so what’s the deal with the holdup Apple?  Please pull your heads out of your tails and work on this!
(Cerulean’s blog post at 60 days)

Adam Wyss (105 Posts) - Website | Twitter | Facebook


Adam Wyss is a tech enthusiast who started off here as an iPaqHQ forum member and has gone though all the Windows Mobile revisions before finally settling on an iPhone 3GS. When not surfing the latest iPhone news, he is a full time student at Ivy Tech Community College majoring in Computer Information Technology.

ADVERTISEMENT

  • http://twitter.com/doogald doogald
  • http://twitter.com/doogald doogald

    I saw a really good story today on theappleblog.com that details some of the hypocrisy of developers who are complaining about the review process.

    http://theappleblog.com/2009/11/19/cut-the-dram...

    Also, the Rogue Amoeba guys, knowing that they had buggy code still being sold and knowing what caused the rejection of their upgrade, could have delivered an update that did not use the icons in question and then fight to include them in a later update, but instead chose to allow a buggy app to keep being sold while they tried to find a reviewer who would not reject them. I understand the principle, but I think that they could have handled this far better than they did.

    I've read what Gruber posted but I disagree with his analysis. Apple's usage guidelines for their copyrights to me says that developers may not use copyrighted images in their products, and that's what Rogue Amoeba did. The fact that Apple is inconsistently applying this rule is troubling, but they have acknowledged that their approval process needed improving.

  • http://twitter.com/mobilitysite/status/6211848317 mobilitysite

    Posted: App Store approvals: Still more transparency needed http://bit.ly/5A6Imm

  • jeffcliff

    There is a lot of buzz around in Iphone app developers’ community that Apple doesn’t follow some uniform strategy for the Iphone application approval. Many developers have already rejected the stiff criteria and announced to stop developing new apps for the iphone but inspite of these agitations and furor we see many different iphone apps are coming rapidly and these apps are the main source of admiration for Iphone. For some exciting iphone app review visit Pro App Reviews

  • jeffcliff

    There is a lot of buzz around in Iphone app developers’ community that Apple doesn’t follow some uniform strategy for the Iphone application approval. Many developers have already rejected the stiff criteria and announced to stop developing new apps for the iphone but inspite of these agitations and furor we see many different iphone apps are coming rapidly and these apps are the main source of admiration for Iphone. For some exciting iphone app review visit Pro App Reviews

Subscription

You can subscribe by e-mail to receive news updates and breaking stories.

Polls

Would you use Bing on an iPhone?

View Results

Loading ... Loading ...

About Mobilitysite

Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : AttValue: " or ' expected in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): ^ in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : attributes construct error in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): ^ in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : Couldn't find end of Start Tag html line 2 in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): ^ in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : Extra content at the end of the document in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Warning: SimpleXMLElement::__construct(): ^ in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144 Fatal error: Uncaught exception 'Exception' with message 'String could not be parsed as XML' in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php:144 Stack trace: #0 /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php(144): SimpleXMLElement->__construct('...') #1 /home/mobilitysite/public_html/wp-content/themes/tinynews/single.php(76): include('/home/mobilitys...') #2 /home/mobilitysite/public_html/wp-includes/template-loader.php(34): include('/home/mobilitys...') #3 /home/mobilitysite/public_html/wp-blog-header.php(16): require_once('/home/mobilitys...') #4 /home/mobilitysite/public_html/index.php(17): require('/home/mobilitys...') #5 {main} thrown in /home/mobilitysite/public_html/wp-content/themes/tinynews/page_sidebar.php on line 144