Guideline 4.2
Guideline 4.2 rejections often mean Apple believes the app is too simple, too website-like, too empty, or not useful enough as a standalone iOS app.
The app is mostly a web view, brochure, event listing, PDF wrapper, or thin content shell.
Core functionality is hidden behind login or paid access without reviewer instructions.
Screenshots and metadata fail to show enough native, interactive value.
Add clear native functionality that users can interact with immediately.
Update screenshots to show real in-app value instead of splash or marketing screens.
Explain unique functionality in review notes and metadata.
If you changed the product, list the concrete features added.
If Apple missed existing value, provide a guided test path and screenshots that show it.
Next step
Get a minimum-functionality risk review across metadata, screenshots, and app context.
Get started