visionOS App Review checklist

State the spatial purpose

A visionOS app can be useful as a windowed app, but review and users still benefit from a clear spatial reason. Name whether the app uses depth, scale, shared space, immersive focus, 3D inspection, spatial audio, hands-free interaction, or room-aware context.

If the app is a port, identify the native improvements rather than pretending every screen is immersive. A restrained windowed experience can be stronger than an uncomfortable immersive wrapper.

Test eyes, hands, and fallback input

• Primary controls should be visible, targetable, and reachable without awkward posture.
• Gestures should not conflict with system expectations or require long precision holds.
• Text entry, selection, drag, resize, and dismissal should work with realistic user behavior.
• If controllers, keyboards, or gamepads are supported, the app should explain when they are optional or required.

Review motion and immersion for comfort

Immersion can create delight or discomfort. Test movement speed, camera transitions, depth changes, flashing content, sound, object scale, and how users exit an immersive space. Do not force full immersion for tasks that can be completed safely in a shared space.

AppReviewReady interpretation: create a comfort stop rule. If a tester reports nausea, disorientation, unreadable depth, or difficulty exiting, block the release until the experience is redesigned.

Protect spatial and personal context

1. Check whether the app requests camera, microphone, location, photos, contacts, health, Bluetooth, or other sensitive permissions.
2. Verify privacy labels and policy describe collection and sharing accurately.
3. Avoid showing private information in shared spatial contexts unless the user chooses that display.
4. Test guest, demo, signed-out, and denied-permission states.
5. Confirm screenshots and previews do not imply room understanding or mixed reality capabilities the app does not use.

Write a spatial review route

Review Notes should help a reviewer reach the spatial behavior quickly. If hardware-specific behavior differs from simulator behavior, document which parts were tested on device.

Also record the least capable acceptable path. If the immersive scene is optional, the windowed mode still needs to be coherent. If the immersive scene is the product, the app needs a clear exit path, understandable controls, and a fallback message when required content cannot load.

When the app imports user media, 3D objects, or collaboration content, add sample content that is safe for review. Spatial apps can look empty or broken when the first run depends on a user's private room, file library, or teammate session.

visionOS review route:
Spatial purpose: [window, volume, immersive]
Input required: [hands, eyes, controller]
Comfort-sensitive areas: [motion/depth]
Permissions: [list]
Sample content: [how to load]
Exit path: [how user leaves immersive state]