What reviewers assess.
WHAT REVIEW CHECKS
Whether the application works as described Whether it provides sufficient value Guideline compliance Privacy handling and declarations Permission justifications Payment rules
WHAT COMMONLY CAUSES REJECTION
Crashes or broken features Incomplete functionality or placeholder content Vague permission usage descriptions Requiring an account without justification Applications that are essentially a website wrapper with little added Payment rules not followed Misleading listing content
WHAT THE ACCOUNT POINT MEANS
If an account is not necessary to use the application, requiring one is questioned.
WHAT TO EXPECT
Review taking a day or more, and rejections being normal rather than exceptional.
WHAT TO DO ON REJECTION
Read the specific guideline cited Address the actual issue Respond through the resolution centre, factually
WHAT NOT TO DO
Resubmit without changes Argue Attempt to circumvent
WHAT EXPEDITED REVIEW IS FOR
Genuine urgency, used sparingly.
WHAT TO READ BEFORE BUILDING
The guidelines for the categories you operate in.
WHY BEFORE
Some things cannot be fixed at submission.
