An interview with Apple executives Susan Prescott and Steve Sinclair on building apps for the Vision Pro and how Apple is trying to lure developers to make apps
Apple's Vision Pro headset hasn't launched yet, but already it's become one of the most hotly debated devices on the planet.
Context & Ripple Effects
Before launch, Apple’s core pitch was that developers could bring iOS and iPadOS apps to visionOS through familiar tools, lowering the initial barrier to populating the headset’s software catalog. This interview makes developer recruitment a central part of the product’s go-to-market strategy.
Later coverage sharpened the stakes: developers cited uncertain returns and App Store-policy frustration, while the pace of new Vision Pro apps fell after the early months. The question is therefore not simply whether apps can be built, but whether Apple can create a durable economic case for building them.
First-order effects
- Apple is directly using executive outreach to persuade developers that Vision Pro is a viable application platform before customers can establish demand.
- Developers must decide whether to adapt existing iOS/iPadOS software or commit resources to native visionOS experiences, with Apple’s familiar-tooling pitch reducing technical friction.
Second-order effects
- The early catalog will shape the headset’s perceived usefulness: Apple’s ability to ease iOS and iPadOS apps into visionOS can expand availability quickly, but does not by itself guarantee differentiated apps.
- If developers remain wary of returns, Apple faces pressure to improve the platform proposition beyond technical access; later reports of uncertain ROI and App Store-policy concerns show the limits of outreach alone.
Third-order effects
- Vision Pro’s platform position will increasingly be determined by whether developer incentives produce sustained native software rather than an initial ported-app library.
- The broader headset market is likely to reward platforms that combine distribution, developer economics, and clear use cases; the later search for a “killer app” underscores that unresolved dependency.
The trend: Spatial-computing hardware is becoming an ecosystem competition in which developer economics and software depth matter as much as the device itself.