Google's equivalent of Apple's minimum-functionality guideline: an app has to be stable, complete, and provide real functionality — not a placeholder shell, and not one that crashes on common devices.
Most often caused by testing only on a high-end device and not against Android's much wider hardware/OS fragmentation, so the submitted build crashes on common lower-end configurations.
"Your app crashed during our review, or does not function as described in your app's store listing, per the Functionality policy."
Google expects an app to be stable, complete and useful. A placeholder shell, an app that crashes on common devices or one that does not provide real functionality can be rejected. The most common cause is testing only on a recent, powerful phone, which leaves the build unstable on the many lower-end devices that make up a large share of Android users.
Android runs on thousands of device models, with different screen sizes, chipsets and versions of the system. An app that works on one phone can fail on another, and a broken first impression harms both users and the platform's reputation. By setting a baseline for stability and completeness, Google tries to ensure that anyone who installs an app from Play gets something that works on the device they actually own.
It uses a range of devices in its review and testing processes.
Play tracks stability metrics for apps that are published.
They are similar in spirit, though framed in terms of stability and completeness.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.