watchOS App Review checklist

Name the wrist-first job

Good watch apps do something brief, personal, and timely: glance, record, start, stop, approve, navigate, breathe, pay, track, or respond. If the app only mirrors a long iPhone workflow, the experience can feel incomplete on Apple Watch.

Write the main watch task as a short verb phrase. Then remove screens that do not help that task. This keeps review focused on the value the watch app actually delivers.

Make watch metadata specific

• Description should explain Apple Watch functionality, not only the iPhone app.
• Screenshots should show real watch UI and current features.
• Complication or widget claims should match what ships in the build.
• If an iPhone app is required, explain what can and cannot be done from the watch alone.

Test iPhone-connected and independent states

Watch review should cover paired iPhone available, paired iPhone unavailable, network available, network unavailable, signed-out, and permission-denied states where relevant. The watch app should not leave the reviewer stranded with a spinner when a clear explanation is possible.

AppReviewReady interpretation: if the watch app is a companion, make the companion relationship explicit. If it is independent, prove the core task can complete without opening iPhone.

Verify complications, notifications, and quick actions

1. Add each supported complication or widget surface and check real text lengths.
2. Tap from the complication and confirm the app opens to the matching state.
3. Trigger watch notifications and verify actions do not require hidden iPhone context.
4. Test health, location, Bluetooth, microphone, and notification permissions from watch-relevant flows.
5. Confirm the app handles small-screen errors with short, readable messages.

Give review a watch-specific path

A watch-specific path reduces the chance that the reviewer only tests the iPhone app and misses the intended wrist workflow. Keep the route short because watch tasks should be short.

If the app uses HealthKit, workout sessions, Bluetooth accessories, or background updates, add a second note for the permission state. The reviewer should know whether a sample workout, paired device, or simulated value is needed, and what the watch app shows when that dependency is absent.

Also verify the watch app does not depend on notification timing to reveal its core feature. Review should be able to open the app directly and understand its primary value without waiting for an external trigger.

watchOS review path:
Primary watch task: [verb phrase]
Requires iPhone: [yes/no and why]
Complications/widgets: [list]
Permissions: [list]
Test account setup: [steps]
Expected result: [watch screen/action]