Google reviews Wear OS apps against additional requirements beyond the base Android policy: the watch app has to function meaningfully on its own (not require the phone app open to work), respect battery/complication guidelines, and follow Wear-specific navigation patterns.
Frequently caused by a companion watch app that's effectively non-functional unless the paired phone app is actively open, which Wear OS review treats as not meeting the standalone functionality bar.
"Your Wear OS app does not function independently of its companion phone app, which does not meet the Wear OS compliance requirements for standalone functionality."
Wear OS apps are reviewed against additional requirements beyond the standard Android policy. The watch app must be useful on its own and not depend on the phone app being open, respect battery and complication guidelines and follow Wear-specific navigation patterns. A companion app that does little unless the paired phone app is active is a frequent problem.
A watch is used in short glances and has a small battery, so apps designed for phones do not translate directly. People expect a watch app to work quickly without a phone in hand. The additional rules keep Wear OS apps lightweight, fast and independent, which makes the platform feel reliable and prevents poorly adapted apps from draining the battery or cluttering the experience.
It should provide meaningful functionality on its own.
Yes. Wear OS has its own interface and navigation guidance.
Efficiency is part of the review.
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.