App Content Is Inappropriate
- Apps related to sensitive content, such as porn and gambling, are automatically rejected. They will also not approve content about terrorism, racism, violence, substance abuse. Generally, if your app offends people or encourages them to break the law, you will probably get a rejection approval
- In this case, either you modify the content or not launch it into the Apple Store.
You Have No Privacy Policy
- Apple requires the application to take the user privacy data seriously to comply the GDPR in Europe and various FTC rules in the US.
- To avoid rejection, make sure that users have been aware of the Term Of Use, Privacy Policy.
- It should explain how you use the specific data that you collect: how it’s stored, and whether or not you share it with other third-party entities.
- Lastly, the user has full permission for his own data, even asking to remove it: making a function for request to remove data is a reasonable choice.
Missing Sign in with Apple for third party sign up
- Apps that exclusively use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer Sign in with Apple as an equivalent option
App Wants to Share Personal User Data
- In general, users must have control over their data at all times. Users must notice how and why the application would like to use their data and privacy: photos, location, notification...
- The key is being declaration right and enough permission will avoid you to be rejected in this section.
The App Is a Copy of Another App
- Apps that are cloned from another app on the Apple Store will get rejection. You should come up with a unique app concept.
- Another case is spamming, the same app but multiple variants. For example: same app feature and UI but different theme, data...
Hardware and Software Are Not Compatible
- App can not only run on iPhone but also on iPad as well and vice versa
You’re Using Private API
- Private APIs are the API used internally by Apple. They are undocumented or don't officially documented by Apple. The APIs are not stable and can be changed anytime, so they're less guarantee
- Make sure your code base and even the external libraries don't mess with these or wait for a brutal rejection.
Bugs and Crashes Occur During the Review Process
- If any crash or significant bug or performance issue (ex: http 500, no network, lagging...) appears during the process, the app will be rejected immediately. Those who perform the review process are human and they test on the physical device (not on an emulator).
- To avoid this, please take the QA step seriously.
Unusually Long Load Times
- Apps that take long loading times may cause poor user experience, therefore, could be rejected. To prevent this kind of issue, simplify the user interface and optimize your code to make it run faster, compressing images and assets to reduce load times.
- For apps that need to connect to a server, you only fetch required data and utilize the caching mechanism.
- For cold startup, it's a good idea to add a splash screen
Placeholder Content Is Still in the App
- A placeholder or dummy content is a sign of an uncompleted app. A not yet complete app violates the App Store rules, so the app will be rejected.
- Inspecting every corner of your app ensures that you catch these simple mistakes before submission.
Broken Links in the App
- Broken links in apps will also be rejected by Apple. For reviewers, it's a sign of poor performance application may affect to user. Thoroughly check all your app links before submit the app.
App Appears to Be Unfinished
- Even if the app is complete, the mistake in app name (app beta, app dev, app demo...) or build version (0.x) may get your app violate the incomplete app case. The app to submit to stores are considered ready for distribution.
- Be aware.
Incomplete or Inaccurate Metadata
- This is about the meta data you put on the App Store Dashboard: app descriptions, screenshots, age ratings, payment options, and privacy information. The key is honest, sincere and transparent. Do not cheat.
- Remember to upload screenshots for every screen size on the iPhone/ iPad. Do not use any other exotic template device (ex: Android) but an iPhone/iPad.
- Do not mention any keywords about different platforms (ex: Android)
Low-Quality UI
- Apple has provided a detailed description of how an app should be designed to comply with their platform (Human Interface Guidelines).
- A poor UI design that fails to meet standards may get rejected.
- Please make sure your app looks fantastic and consistent across all Apple devices.
No comments:
Post a Comment