Is visionOS Worth Building For?

The honest answer for most companies today is "not yet, and here is what to do instead". For a specific minority it is clearly yes. The distinction is about whether spatial computing solves a problem you actually have.

The commercial reality

Vision Pro's installed base is small relative to iPhone by orders of magnitude, and the device is expensive. Any business case resting on volume does not currently work. That is not a permanent verdict — it is a statement about now, and it should be the starting point of an honest conversation rather than something discovered after spending.

When it genuinely makes sense

The value is spatial, not incidental
Reviewing a building at true scale. Understanding a molecule from inside. Training on equipment too dangerous or expensive to practise on. If a flat screen loses something essential, spatial computing earns its cost.
Enterprise deployment with known ROI
Where the comparison is not "versus an iPad app" but "versus flying trainers to a facility", the device cost stops being the deciding factor. Most current viable visionOS work is enterprise.
Strategic positioning with eyes open
Some organisations build to learn the platform and be credible early. That is a legitimate marketing and capability investment, provided it is budgeted as one rather than expected to return revenue.
You already have the 3D content
If you hold optimised 3D assets from other work, the marginal cost drops enormously and the calculation changes.

When it does not

If your app is fundamentally lists, forms, and content, visionOS adds a large window and little else. If you have not shipped a solid iOS app yet, that is the higher-return investment by a wide margin. If the business case is "be early", check whether that is strategy or fear of missing out — the two feel identical and cost very differently.

What it costs

A simple compatible app — an existing iPad app running in a window — is close to free, and worth doing if you already ship for iPad. Check it behaves sensibly and leave it.

A genuine spatial experience is a different project. Budget in the range of an AR app or higher: 3D content, spatial interaction design without established convention, and testing that requires the actual hardware. See cost to build an AR app for the cost structure, which is similar.

The cheaper first step

If you build for iPhone or iPad with SwiftUI, your app likely already runs on visionOS in compatibility mode. Test it, fix anything that looks wrong, and ship that. You get a presence on the platform for very little, and you learn something real about whether users want it before committing to a spatial build.

This is the recommendation for most companies asking the question: do the cheap version, watch the numbers, and revisit in a year.

What to build instead, usually

For most businesses, phone-based AR reaches vastly more people at a fraction of the cost, and ARKit is mature. If your goal is spatial interaction with customers rather than platform presence, iPhone AR is where the users are. We build both — our own AR title is iPhone-based for exactly this reason.

Our position

We build for visionOS and we will tell you when we think you should not. If your case is enterprise with clear ROI, or genuinely spatial value, it is a good investment. If it is a consumer app hoping for volume, we would rather point you at iPhone AR and revisit visionOS when the installed base justifies it.

Frequently asked questions

Is visionOS worth developing for?

For most consumer businesses, not yet, because the installed base is small relative to iPhone. It makes clear sense for enterprise deployments with measurable ROI, genuinely spatial use cases where a flat screen loses something essential, and companies that already hold optimised 3D content.

How much does a visionOS app cost to build?

A compatibility-mode version of an existing iPad app is close to free. A genuine spatial experience costs in the range of an AR app or higher, driven by 3D content creation, spatial interaction design, and testing that requires the actual hardware.

Does my iPad app already work on Vision Pro?

Very likely, in compatibility mode. If you build with SwiftUI for iPhone or iPad, testing and polishing that compatibility version is the cheapest way to have a presence on the platform.

Should I build for visionOS or iPhone AR?

For reaching customers, iPhone AR reaches vastly more people at a fraction of the cost and ARKit is mature. visionOS makes sense when the spatial fidelity genuinely matters or for enterprise scenarios with clear returns.

What kinds of visionOS apps actually succeed today?

Mostly enterprise applications where the comparison is against expensive alternatives, such as training on equipment that is dangerous or costly to practise on, and design review at true physical scale.

Talk to us about your build

KIDA Studios builds custom software, apps, games, AR and XR across Apple platforms, Windows, Android, web, and embedded. If you have a project in mind, a short discovery call is the fastest way to get a realistic scope and number.

Start a project