I’m developing two complementary developer tools: Reality Prep Pro on macOS and Reality Prep Preview on visionOS.
The workflow I’m trying to solve is:
Mac: prepare and validate a USDZ
Vision Pro: verify that exact USDZ on-device
Mac: bring the device evidence back and associate it with the exact asset revision
I currently use the USDZ’s SHA-256 as the authoritative identity. If the asset bytes later change, the previous Vision Pro evidence is treated as stale and a re-test is recommended.
Existing USDZ→USDZ preparation is package-preserving, so non-texture payloads such as animation/rigging data are not unnecessarily re-authored.
I’d be interested in hearing from other RealityKit / Reality Composer Pro developers:
Is this similar to how you currently handle asset provenance between desktop preparation and real-device testing?
Are there any Apple frameworks or established visionOS practices you would recommend for strengthening this kind of revision-to-device-evidence workflow?