Apple’s WWDC keynote on Monday was one of those rare events where you watch a product announcement and genuinely don’t know what to think. The Apple Vision Pro is a $3,499 mixed reality headset with an entirely new operating system — visionOS — and a full development SDK. After spending the week digesting the sessions and documentation, I have thoughts. Some excited. Some skeptical. All uncertain.
The Hardware Proposition#
Let me get the specs out of the way: dual Apple M2 and R1 chips, micro-OLED displays with reportedly stunning resolution, eye tracking, hand tracking, and a spatial audio system. The R1 chip is dedicated to processing sensor data with a claimed 12-millisecond photon-to-display latency, which is critical for avoiding motion sickness.
At $3,499, this is clearly a developer kit and early-adopter product disguised as a consumer launch. Apple isn’t saying that out loud — they’ve positioned it as “one more thing” with slick marketing — but the pricing tells the story. The interesting question isn’t whether consumers will buy this in 2024 when it ships. The interesting question is whether developers will build for it.
visionOS: A Genuine Platform Play#
This is where WWDC gets interesting from a technical perspective. Apple didn’t just slap ARKit onto an iPad strapped to your face. visionOS is a new platform with its own UI paradigms, its own spatial layout system, and deep integration with the existing Apple development ecosystem.
The development model comes in three tiers:
Compatible apps: Existing iPad and iPhone apps run in visionOS with minimal or no modification. They appear as flat windows in the spatial environment. This is Apple’s clever way of ensuring the platform has apps from day one — your SwiftUI app probably already works.
Window-based spatial apps: Using the new SwiftUI extensions for visionOS, you can create apps with windows that exist in 3D space. Windows can have depth, respond to spatial input (eye tracking + hand gestures), and coexist with other apps in the shared space. If you know SwiftUI, the learning curve here is manageable.
Fully immersive experiences: Using RealityKit and the new RealityKit APIs, you can build fully immersive applications that take over the user’s entire visual field. This is the games, training simulations, and specialized professional tools tier.
The developer documentation is already comprehensive, and Xcode 15 beta includes a visionOS simulator. Apple has clearly been working on the developer tools for years — the SDK doesn’t feel rushed.
SwiftUI as the Foundation#
The most significant technical decision Apple made is centering visionOS development on SwiftUI. If you’ve been building iOS apps with UIKit and have been putting off the SwiftUI migration, Apple just gave you a very compelling reason to accelerate that transition.
The new spatial APIs extend SwiftUI’s declarative model in ways that feel natural. You can add depth to views, create 3D objects using Model3D, and define volumetric windows with WindowGroup using the .volumetric window style. The gesture system extends to spatial interactions — a tap is now a pinch, a long press is a pinch-and-hold, and custom gestures can use eye tracking data.
For web developers, Apple also announced that Safari on visionOS supports WebXR, which means web-based spatial experiences are possible without native development. Given how important the web has been for platform adoption historically, this is a smart inclusion.
The Developer Economics Question#
Here’s where my skepticism kicks in. Every new Apple platform starts with a gold rush of developer enthusiasm, followed by the hard reality of user base economics. The Apple Watch went through this cycle — early apps were pulled by major developers when usage didn’t justify the investment. Apple TV had a similar trajectory.
Vision Pro at $3,499 will have a small initial user base. Very small. Apple will probably sell it in the hundreds of thousands in the first year, maybe low millions if we’re optimistic. That means the addressable market for paid visionOS apps is tiny. The developers who build for it initially will be doing so as a strategic bet, not because the near-term economics make sense.
The counterargument is that compatible iPad apps work out of the box, so there’s no incremental cost for basic support. And Apple has a track record of driving platform adoption through iterative hardware improvements and price reductions. If Vision Pro follows the trajectory of AirPods — starting premium and eventually becoming mainstream — the early developers will have a significant advantage.
What This Means for Development Teams#
If you’re leading a software team, here’s my pragmatic advice:
- Don’t drop everything to build for visionOS. The user base won’t justify significant investment for at least 2-3 years.
- Do invest in SwiftUI if you haven’t. It’s now clearly Apple’s future across all platforms, and visionOS is the strongest signal yet.
- Evaluate your compatibility story. If you have an iPad app, test it in the visionOS simulator when Xcode 15 is stable. Fix any issues so you’re on the platform from launch.
- Explore if your domain has a spatial computing angle. Data visualization, 3D modeling, remote collaboration, and training are all domains where spatial computing could be genuinely transformative.
- Watch the enterprise play. Apple is clearly interested in professional use cases — the custom optic inserts for prescription lenses, the emphasis on productivity workflows, and the enterprise management capabilities suggest they see business adoption as important.
My Take#
I’ve watched every major computing platform launch of the last thirty years, and the Vision Pro reveal has a quality that reminds me of the original iPhone announcement. Not because the first product will be perfect — it won’t be — but because Apple has clearly thought deeply about the software platform, not just the hardware. The developer tools are mature, the migration path from existing skills is gentle, and the integration with the Apple ecosystem is thorough.
That said, I’m not buying one on launch day, and I’m not pivoting any of my projects to visionOS yet. The smart play is to invest in SwiftUI skills, keep an eye on the developer community’s early experiments, and be ready to move when the user base justifies it. Apple has planted a flag in spatial computing. Whether that flag marks the next revolution or another interesting-but-niche platform remains to be seen. The developer tools, at least, suggest Apple is betting heavily on the former.
