What to improve
Add real native functionality or make existing functionality easier for reviewers to find.
Update screenshots and metadata to show the useful parts of the app, not only marketing screens.
Rejection guides
Rejection guide
Minimum functionality rejection: prove the app has enough value
Apple uses Guideline 4.2 when an app appears too thin, too static, too web-like, or not useful enough as a standalone iOS app.
Developers rejected for minimum functionality. Guideline 4.2
Safer reply structure
List concrete changes rather than saying the app is useful.
Include reviewer notes that guide Apple to the strongest native flows.
Next step
Analyze your 4.2 rejection
Get a fix-vs-appeal recommendation for your minimum functionality rejection.
Get started