Seeking Advice: Navigating App Review for Complex, Server-Dependent iOS App

Hello, fellow developers and Apple engineers,

I'm reaching out to seek advice and insights on a challenge I've encountered during the app review process for a particularly complex iOS app. Our app is designed to manage communal activities for cities, working in conjunction with desktop software/server, which makes it both large and intricate. Its primary users are specific companies, such as Municipal utilities, across various cities in Germany, each with over 100 devices.

The core of the challenge lies in the app review stage. Due to the app's complexity and the necessity for specialized knowledge to understand its full functionality, it seems that the review team faces difficulties in evaluating the app, leading to rejections. It's clear that without training or a deep dive into the app and its server-side components, grasping its utility and operational nuances is challenging.

We've attempted to provide detailed documentation but we're still encountering hurdles. Here are some specific questions and areas where we'd appreciate your guidance:

  1. Best Practices for Submitting Complex Apps: Are there recommended strategies or best practices for submitting apps that require a deep understanding of specific, non-public functionalities?

  2. Communication with Reviewers: Is there an effective way to communicate the necessity of our app's complexity and its server-dependent nature to the review team? Any tips on ensuring this communication is as clear and constructive as possible would be invaluable.

  3. Documentation for Review: What kind of documentation have you found most effective in aiding the review process for complex applications? Are there formats or templates that seem to work best?

  4. Appealing Review Decisions: For those who have gone through the appeal process with similarly complex apps, what was your experience? How can one effectively convey the app's value and operational context in an appeal?

We're committed to ensuring our app meets Apple's standards while providing vital services to our clients. Any insights, advice, or shared experiences in navigating the app review process for similar applications would be greatly appreciated.

Thank you in advance for your time and help.

Best regards,

Dominik

Up vote post of DFrankov Down vote post of DFrankov
340 views
Posted by
DFrankov
Reply
Add a Comment

Replies

I think you misunderstand app review. They do about 4 things, in my experience:

  1. ”Virus scan”-type analysis of the app to see if you have included anything naughty. Not a problem except when they have false positives.

  2. An automated analysis of your app metadata to see if you mention Android or anything else they don’t like.

  3. They run the app once to see if it crashes on launch.

  4. If you have in-app purchase they will try to make sure that they work.

Just submit your app and see what happens. If they reject it, don’t try to “communicate” or “document”, just do exactly what they tell you to do and resubmit.

Posted by
endecotp
Up vote reply of endecotp Down vote reply of endecotp
Add a Comment

If you've received a message about issues with an app, the best way to contact App Review is by replying to the message in App Store Connect. You will be contacted by a specialist familiar with our review of your app who can answer your questions.

You may also use the Apple Developer Contact Us page to request an update on our review of an app or request a call with an Apple representative.

You can also sign up for a session with the App Review team with Meet with Apple Experts for developers. You will need to sign in with your Developer ID and select "Request a one-on-one App Review consultation". An App Review Specialist will help you with any questions you have about the review process.

Posted by
BusterBrown17
Up vote reply of BusterBrown17 Down vote reply of BusterBrown17
Add a Comment