Google Play limited Functionality and Content policy: fixes and checks

A static text page, PDF wrapper, or single-wallpaper app can fall short of Google’s functionality and content requirements. The issue is what users can do with the app, not the tool used to build it.

What to check

List the useful tasks the app supports. Distinguish functioning features from buttons that only open a document, repeat a page, or show an ad.

Check the experience before and after login. If the app needs an account or data to demonstrate its value, reviewers need access to a representative populated account.

How to address the rejection

Build the missing utility or content depth around the app’s actual purpose. For example, a reference tool might need useful navigation, search, saved material, or task-specific interaction. Adding arbitrary native features isn’t a guaranteed approval formula.

Test the complete user task and show it in review notes. If the functionality already existed but reviewers couldn’t reach it, correct access and explain the steps. Avoid promising future features as the reason the current build should pass.