Oh ic what you mean, i was thinking that they wanted a dialog of when it connected, but you’re saying they wanted a dialog when it lost it’s connection?

Kinda seems a little odd, i can see that you would want to notify users as to why the map isn’t working, but you’d think that users would pick up on that pretty fast.

If an internet connection is not available, PlaceTagger cannot load its maps. In the rejected build, it simply did not show the map (it kept the logo on screen). Our reasoning was since location data can still be recorded, there was no reason for user interaction (why make someone hit a button when the primary purpose is still being achieved?).

I suppose users could use the application with the map up all the time, but with the limited battery life of iPhone, we expect they’ll just put it in their pocket so the screen will shut off (ala the proximity sensor) and focus on taking pictures. Given that the purpose of this app is to record location data and later geotag photos, we believe not seeing the map (and more importantly not bothering a user who’s trying to take pictures) is the right thing to do. Perhaps Apple’s reviewer disagrees. That’s fine. We added a label and it is what it is. That doesn’t change the frustration that comes along with feeling like 3 weeks of your time have been wasted.

These issues seem to crop up over and over for silly things (imo, poorly trained folks who misinterpret the UI guidelines..). In this case, we really believe it’s nonsense. There are other cases where the rejection decisions are entirely valid.

I can understand why apple rejected it, it’s just too bad that it’s the third time around being rejected. Also there should be an option to not allow the app to use the internet, and to make apple really happy you should have a dialog box come up the first time it tries to connect to a network just to warn the user.

I am often surprised that people expect that much from the reviewers. Keep in mind, the reviewers aren’t programmers. With Apple’s workload, I bet all the programmers are doing development, QA if not development, developer support if not QA, tech documentation if not support….

You get my idea.

They may have some programming training, but they aren’t gods and they can only make guesses how you implement your code. Heck, if I see your app running, will I assume it is using network?

They may be wrong. Everyone can be wrong. So what? If you are not using connection, tell them that, offer to show your code. Tell them to turn iPhone into flight mode and test again.

After all, reviewers are human too.

No, a weeks worth of lost sales will not break our company, but losing any sales because of Apple’s mistake is unjust. That’s the point.

I hope you get through this time but I honestly don’t know what the rally and cry is about. Standard interfaces = better understood flow for all users. Perfect? no. Apple to the core for all of its products from day one? oh yes.

and no, not a zealot. I have several OSes and enjoy them all and wouldn’t pick just one.