I’m looking for advice on App Store positioning for a slightly unusual developer-tool workflow. I have: Reality Prep Pro — macOS Prepares, validates and optimizes spatial assets. Reality Prep Preview — visionOS Verifies the resulting USDZ on Vision Pro and returns device evidence to the Mac workflow. The value is primarily in using them together: prepare on Mac → verify on Vision Pro → return evidence → detect when the asset changes and needs re-testing. Both apps can stand alone, but they were designed as complementary tools. For anyone who has marketed companion apps across Apple platforms: would you position the App Store pages primarily around each individual app, or make the cross-platform workflow the central story? I’m especially interested in approaches that remain clear to users without making either product page dependent on the other app.

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?