Google Play functionality, Content, and User Experience policy: fixes and checks

Google expects an app to provide useful content or functionality and a stable experience. A successful install alone doesn’t establish that the app is ready for users.

What to check

Complete the main task on a fresh install. Inspect empty states, login, content loading, permissions, and network failure. Check whether the app offers enough actual utility beyond static material.

Use the specific finding to separate a broken implementation from a limited product. Fixing a crash won’t necessarily address an app with no meaningful function, and adding content won’t repair a frozen startup screen.

How to address the rejection

Resolve the affected behavior or expand the app’s useful functionality. Supply working reviewer access and keep required backend services available during review.

Test the exact submitted artifact across supported Android versions and common screen sizes. Document the feature path and the corrected failure. The child policies below explain the checks for limited content and broken functionality in more detail.