I guess most people here don't write iPhone apps. Here's to clear things up where I can: - No way for small bug fixes to jump the queue. There is, you can get

I guess most people here don't write iPhone apps. Here's to clear things up where I can: - No way for small bug fixes to jump the queue. There is, you can get them in within a few days. Not immediate, but it helps a lot. - AFAIK, future releases are not routed through the same reviewer as previous versions, resulting in nonsensical rejections for previously existing characteristics. Not the same reviewer. But just speaking in general, this is also a positive point: if an app should really be rejected, but wasn't due to a lapse by a certain reviewer, it can still be rejected by another reviewer in another version. Makes sense. (well, you can say just skip the review process totally or enforce some way to make every reviewer have the same standard, but we know the world's not perfect, and we make do with what we have). - No feedback mechanism on your place in line. The wait would be a lot of more tolerable if I knew I knew how many days or weeks it should take, on average. Actually it's been months since they started showing the average number of days X% of updates wait (~2 weeks for ~98% so far). And for the past few weeks, they have started showing the status for each update posted. ie. pending review, reviewing, rejected, etc. - Simply put, Apple hasn't made developer relations a high priority, which is unfortunate; failure to do so in the 80s and 90s is part of what kept Macs in single-digit market share. iPhone may be king of the market now, but pissing off devs is not a good way to stay there. This isn't right. Apple has handled developer relations very well for OS X app developers. From the outside, it almost looks like iPhone dev relations is handled by an entirely different group of people.