Apps distributed for use on Android Auto have to follow driver-distraction-focused design rules on top of standard Play policy — no video playback, no manual text entry, and simplified interaction patterns suited to glancing rather than sustained attention while the car is in motion.
A common cause is a media or navigation app that ports its phone UI to the car screen without adapting it, keeping interactions (like free-text search) that Android Auto's review explicitly disallows while driving.
"Your app's Android Auto interface allows free-text input or video playback while the vehicle is in motion, which does not meet Android Auto's distraction requirements."
Apps made for Android Auto follow extra rules built around driver distraction. They must avoid video playback and manual text entry and use simplified interactions suited to quick glances while a car is moving. Developers who move a phone interface to the car screen unchanged often keep features, such as free-text search, that the programme does not allow.
A driver's attention is a safety matter, so the car screen is held to a different standard from a phone. Interactions that are fine on the sofa can be dangerous at speed. The programme limits what an app can present and how it can be controlled, so that apps in cars support the drive without competing with it. Android Auto review is stricter for the same reason.
Categories such as media, messaging and navigation, with their own templates and limits.
The programme has specific rules, so the current policy should be checked.
Yes. Android Auto features are reviewed against additional requirements.
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.