Granted that we hear about all the frustration, the rejections, the waiting game, etc…
But considering the 65k apps approved in the last year or so, I cannot help but think Apple is doing an outstanding job. Across the more than handful applications I have personally submitted or been involved with, all interactions with the app review team have been professional and even friendly.
One may argue that the process is overkill and unduly lengthy, however, I find comfort in knowing that Apple is both raising the bar by making sure developers stick to the “minimum standard” guidelines which ensures a fairly consistent common base for the end users, both in terms of UI and in terms of security. Not having this scrutiny would most certainly render the iPhone experience both very buggy and very unsafe for my end users (and therefore jeopardize my prospect base & target audience).
Moreover, this process has taught and forced me to include “best practice” in our iPhone app developments. I have had some “silly” rejections at first, such as lack of end-user warning in case the app was used in airplane mode: clearly, why would I need to notify the end user that the app is not managing to connect because they are in airplane mode; end-users should know better since they triggered the airplane mode in the first place!!! Well, Apple tells you in section X.Y.Z that you should take care of that. Of course, I had not digested the entire guidelines document, so I had failed to include this level of feedback, and learnt the hard way. And after thinking about it, Apple is right to make sure my end users are told why my app is not functioning; a simple reminder will educate the end-user and ensure a better experience both of the iPhone and my app, and vice-versa.
Moreover, I’ve included this “warning message” in all subsequent apps; and the review team has never bothered me with this again, and rightly so. I’ve therefore built into my practice, by force, a better experience going forward. And Apple has made sure that we, the developer community, do so going forward. Yes, Apple has a few tricks to teach seasoned developers!
Long story short: the approval process is quite a daunting task, and I’m sure Apple has invested quite a lot of resources into it already. Recent interventions by Phil Schiller show that they are listening, and care about improving the process. Curious to see how this pans out in other app store initiatives, and eagerly waiting to see how the Android community will manage this, with possibly even more pressure…
There is room for immediate improvement for sure: lack of transparency between submission and expected release date (often: ASAP), and feedback rounds are sequential (the review team will not give us a wash list, but instead give us each pain point one at a time, forcing us to go through week-long iteration cycles). I feel for those that are waiting for a very long time - though I would never wait sitting idle, and instead would email Apple with additional info about the app, it’s intent, it’s way of working, etc… my waiting time has been at best 4 days, and at most 13 days; and 4 days is already frustrating. I agree that Apple should be more transparent about where they are at, even if it’s just to say: “5 more days until processing (position : 250 in the queue)”, or “pending escalation (reason: not sure about privacy)”, etc… That would help tremendously.
I am confident Apple will fix and improve this process going forward.
Meanwhile, I am proud to say that we released the @appsfire iPhone app (http://appsfire.com/4iPhone) in one go (no iteration with the review team), with a 13 day span between submission and approval (slightly below the current “average waiting time”). With regards to Apple, I am sure the track record with them, the experience and understanding of how Apple caters to its consumer world helps optimizing all of this. Again, hats off and keep up the excellent work Apple. The expectations are high and that’s a good thing.
Yann.