iOS App Distribution

Chances are, your app will probably get rejected at least once through development. This can be disappointing, but there are things you can do to avoid that potential rejection before submission. The link to the App Store Review web page is in the author’s notes for this episode, and it contains some common issues encountered during the review process, and how to avoid them. Let’s take a quick look at some of them now:

Crashes and bugs. Starting out with the obvious set of issues here, if your app crashes, or has some glaring bugs that impact functionality, your app will get rejected. Take advantage of TestFlight to make sure you’ve smashed as many bugs as possible before submission.

Broken links and placeholder content. When you have links in your app that don’t go anywhere, or placeholder content for images and text, it means your app isn’t ready for prime time. Make sure links work, and placeholder content is replaced with real images or text (or that it will get replaced with actual content at runtime)

Incomplete information. Make sure all of the information in your App Store record is filled out correctly. This may include providing some documentation for certain types of apps, such as apps for kids, or if your app works with medical hardware.

Inaccurate screenshots. Staying in the metadata arena, make sure the screenshots you provide in App Store Connect accurately communicate value and functionality.

Misleading users. A surefire way to get your app rejected is to give your users the impression your app is something that, in reality, it is not.

There are several other common issues you can read about on the App Store Review page.

I’ve also put a link to a Tech Talk entitled “Tips for preventing common review issues” in the author’s notes for this episode. Be sure to check it out!

With this information in hand, it’s time to actually submit your app for review. In the next episode, you’ll dive a little deeper into what that means.