3 ms·

In my experience the appeal board are just as stupid as the reviewer cited in the post. It was like my app was evaluated by a random different reviewer. Someth

In my experience the appeal board are just as stupid as the reviewer cited in the post. It was like my app was evaluated by a random different reviewer. Something is strange about the whole app review process. It's been problematic for years. Apple could fix it if they had the incentive. IMO they do have an incentive (more developers, more sales etc) but something else is preventing the process from improving. Lately it seems like the review process is becoming worse. Perhaps it's company politics? The VP of whatever group is ultimately in charge of hiring reviewers, adjusting policies etc may be standing in the way. However given the explosion of the mobile ecosystem it seems unlikely that organizational politics would come first. One side note: for my last app that was reviewed and rejected multiple times (once by the appeal board) it seemed like the reviewers were really trying hard to make the app crash. I log almost everything users do in the app. Since the only people with copies of the app were myself and Apple I could see the reviewer(s) activity. If you've tested iOS apps that use even basic tableViews populated with remote data you know that swiping vigorously, pushing and popping viewControllers quickly etc can wring out some funny corner cases. It seems like the reviewer was trying to find one as a pretense for rejecting the app when the real reason was something they didn't want to say. Apparently they didn't find anything and went with "app is just a re-packaged website without enough native iOS functionality" when the entire app uses native iOS features.

eridius 14y ago
Are you actually complaining that the reviewer was performing some QA-like functionality? That's surprising. You may also be misinterpreting. Quickly going through an entire app (which is what I'd expect a reviewer [who's actually testing the app] to do) is necessarily going to involve lots of really quick pushes and pops of VCs and swipes and whatnot. So no, I don't think the reviewer was trying to find some pretext to reject you. That doesn't even make sense. Why would a reviewer need that?
- spaghetti 14y ago
  Perhaps I did misinterpret. However the given reason for rejecting the app suggests there's something else going on behind the scenes. "Your app doesn't have enough native iOS functionality" is obviously BS when the app's primary navigation is a tableView, uses the accelerometer and in general is filled with native iOS functionality. Maybe the app's use of Google maps was frowned upon because of some tense relationship between the two companies. So instead of rejecting the app for "using Google maps because we don't feel comfortable with that" the reviewer tried to find a crash. When they couldn't they gave me the hilarious BS reasons. Hence a pretense to reject the app could make the reviewer's life easier.

eridius 14y ago

Are you actually complaining that the reviewer was performing some QA-like functionality? That's surprising. You may also be misinterpreting. Quickly going through an entire app (which is what I'd expect a reviewer [who's actually testing the app] to do) is necessarily going to involve lots of really quick pushes and pops of VCs and swipes and whatnot. So no, I don't think the reviewer was trying to find some pretext to reject you. That doesn't even make sense. Why would a reviewer need that?

spaghetti 14y ago
Perhaps I did misinterpret. However the given reason for rejecting the app suggests there's something else going on behind the scenes. "Your app doesn't have enough native iOS functionality" is obviously BS when the app's primary navigation is a tableView, uses the accelerometer and in general is filled with native iOS functionality. Maybe the app's use of Google maps was frowned upon because of some tense relationship between the two companies. So instead of rejecting the app for "using Google maps because we don't feel comfortable with that" the reviewer tried to find a crash. When they couldn't they gave me the hilarious BS reasons. Hence a pretense to reject the app could make the reviewer's life easier.