App Rejected for Design: UI and Functionality Requirements

Apple's Design Rejection Triggers

Apple's Guideline 4 covers Design. Common rejection triggers include: minimum functionality not met (your app must do more than a website would), apps that are essentially web wrappers without native features, UI that does not follow basic Human Interface Guidelines (unusable at standard text sizes, tap targets too small), apps that look incomplete or have placeholder content, and apps that duplicate built-in iOS functionality without meaningful enhancement.

Google's Design Requirements

Google is generally less prescriptive about visual design but enforces: minimum quality standards (app must not crash, hang, or produce ANR dialogs during normal use), apps must provide meaningful functionality beyond what a mobile website offers, apps must not use deceptive design patterns (hidden costs, forced consent, interface interference), and accessibility requirements for apps targeting specific user groups.

Passing Design Review

Build something that works well natively. If your app could be a simple website, add features that leverage the device (push notifications, offline mode, camera integration). Test on multiple screen sizes. Use standard UI patterns where appropriate. Ensure all text is readable and all buttons are tappable at standard sizes. Remove all placeholder content and test accounts before submission.

Frequently Asked Questions

Related Resources