Updated August 2026 against the iOS 27 and visionOS 27 developer betas. We refresh this post each June after WWDC.
WWDC 2026 was a quieter year for augmented reality headlines than 2023 (Vision Pro) or 2025 (the SceneKit deprecation), and a more consequential one for anybody shipping AR in production. The theme was convergence: ARKit on iPhone and ARKit on Vision Pro are becoming one platform with two form factors. Here is what changed, and what we are telling clients to do about it before the public release in September.
Cross-platform ARKit reference objects
The headline for enterprise AR. Reference objects — the trained models ARKit uses to recognize and track a specific physical thing — are now a single format that works on both iOS 27 and visionOS 27. Train once in Create ML, ship one .referenceobject, track on an iPhone and on a Vision Pro.
Until now these were two pipelines. iOS used ARReferenceObject scanned with ARKit's object-scanning flow; visionOS used a photogrammetry-derived reference object trained in Create ML. Teams supporting both devices maintained both, and most did not bother, which in practice meant "Vision Pro only" or "iPhone only" for object-tracking features.
What it means for your roadmap. If you have an object-tracking app on one platform, the cost of adding the other just dropped to an adapter layer around the anchor updates. Our object tracking tutorial walks through the same reference object on both devices, with code. If you have been putting off object tracking because of the two-pipeline problem, that reason is gone.
Spatial Accessories on visionOS 27
visionOS 27 introduces the Spatial Accessories framework: first-class support for tracked physical accessories — controllers, styluses, and tools — with their pose available to apps in immersive spaces. Hand and eye input remain the default on Vision Pro, but there are workloads where a tracked physical tool is simply better: precise placement in design review, simulation and training that needs the feel of a real instrument, and games.
What it means for your roadmap. For most business apps, nothing immediately. For training, simulation, and creative tools, this is the feature that unlocks the use cases where hand tracking was never going to be precise enough. Plan it as an enhancement to an existing immersive experience, not a reason to build one.
visionOS 27 and iOS 27 platform notes
Smaller items that add up:
- RealityKit parity continues to improve across iOS, macOS, and visionOS. Code written against
RealityViewon iOS 18 or later is increasingly a straight port to a visionOS volume or immersive space. - SceneKit is still deprecated and still in critical-bug-only maintenance. Nothing at WWDC 2026 reversed that; if anything, the cross-platform story makes the RealityKit migration more urgent, because none of the new capabilities are reachable from a SceneKit renderer. See our 12-month plan.
- Reality Composer Pro remains the authoring tool for RealityKit content and shader graphs, and the right place to standardize an asset pipeline that serves both devices.
What we are telling clients
If you ship AR on iPhone only. Adopt iOS 27's cross-platform reference objects when they release in September even if Vision Pro is not on your roadmap; the new training flow is better than the legacy ARKit object scan, and you get the visionOS option for free. Make sure you are on RealityKit; if you are not, start the migration now.
If you ship on Vision Pro only. Your reference objects already work on iOS 27 with minimal change. The question is whether an iPhone version of your app would reach users who will never wear a headset. For field service, retail, and logistics the answer is usually yes.
If you have been waiting to see whether Vision Pro matters. The convergence at WWDC 2026 is Apple's answer: the investment in ARKit on iPhone is the same investment as ARKit on Vision Pro. Building on RealityKit today is the way to keep both options open without building twice.
If you are on the betas. API names can still move between now and the September release. We have flagged beta-dependent code in our tutorials; re-check it against the release SDK before shipping.
A note on timing
Public release of iOS 27 and visionOS 27 is expected in September 2026, as usual. Apps that adopt the cross-platform reference objects at launch will have the feature for the holiday quarter; apps that wait for the dust to settle will be adopting it in the new year. For enterprise deployments with device-management lead times, that difference matters.
Want a roadmap conversation about what WWDC 2026 changes for your AR product specifically? Talk to a RealityRogue consultant.