Skip to content
AppDues
Log in
Contact salesSign up

Monetizing a visionOS App: Market Size, Conversion and Model Choice

A small early audience can still pay well, but only if the business model fits how people actually use a headset. This guide compares the first-year market with earlier Apple platforms, explains why conversion can look unusually strong, and gives a practical way to choose among ads, paid downloads, one-time purchases and subscriptions.

First-year market size: small compared with iPhone, iPad and Watch

The comparison below is about addressable audience, not a verdict on the headset itself. Raw unit counts cannot judge product success, but they do show how many potential customers a developer can reach in year one.

Vision Pro figures were estimates rather than Apple-reported sales. Analyst Ming-Chi Kuo put the first pre-order weekend at 160,000 to 180,000 units, later raised the production order to 700,000 to 800,000 for the year, and the analysis used 800,000 shipped units as a generous first-year projection. Treat that as dated, unverified captured evidence.

Even with that generous projection, the audience was far smaller than earlier Apple launches. The original iPhone sold 270,000 units in 30 hours and one million in 74 days, with many reports putting first-year sales at a little over six million. Because the App Store arrived with the iPhone 3G, the fairer early-store comparison adds the original iPhone to the 3G: the 3G alone sold one million in its opening weekend, with an estimated 20 million in its first year. That combined base helps explain why even niche early iPhone apps could find large audiences.

Later platforms were also much larger. The iPad sold 300,000 on day one and 15 million in year one. Apple Watch had 957,000 preorders and passed 11 million units. Against those numbers, a projected 800,000 Vision Pro units is a niche market, however enthusiastic its owners may be.

Competition for attention was also different. The original App Store launched with about 500 apps. visionOS launched with roughly 600 native apps, a similar count, but Apple also promoted more than one million iPad-compatible apps in the same store. A new visionOS app therefore competes for discovery against a much wider catalogue than the native-app count alone suggests.

Why conversion can be strong despite a small audience

A smaller market does not mean no revenue. It means expectations and pricing need to match the audience. In the author's own apps, conversion to paying was higher on visionOS than on iOS, comparing the visionOS app Spatial Noise with the iOS app Dark Noise. Other visionOS developers reported the same pattern, including for iPad-compatible apps running on the headset.

The likely explanation is audience selection. People who bought an expensive new headset early were less price-sensitive, more technology-forward, and actively hunting for novel experiences. One quoted user put it plainly: they had bought things on Vision Pro they would never have bought on a phone, simply to discover what the experience was like, including inexpensive games deleted after half a minute.

That behaviour is useful but fragile. It rewards a distinctive first encounter and a price that feels acceptable for experimentation. It does not guarantee that the same users will keep paying month after month, because many may not yet know whether they will use the headset regularly at all.

Choosing a model: ads, paid up-front, in-app purchases or subscriptions

Free with ads: Third-party ad SDKs, such as AdMob or Facebook Ads, are relatively straightforward to add. Revenue rises with engagement, so apps that deliver frequent value are rewarded. The weakness is scale: ads need a large, frequently active base, and visionOS has neither yet. Ad networks also limit control over the experience, and blocking profitable categories such as gambling reduces income. This model fits apps that already have, or genuinely need, a large audience and high-frequency use.

Paid up-front: This is the simplest model to ship, since the price is set at release and no purchase logic is built into the app. Lifetime value arrives immediately and does not depend on continued use, which suits hobby projects and one-time experiences. The trade-off is no repeat revenue, a higher download barrier, and danger when per-user costs continue after the sale, as with weather or AI features backed by usage-based APIs. It fits quick recoupment, one-off experiences, and apps without recurring costs.

In-app purchases: A free download lowers the barrier, letting people judge the app after onboarding or a free tier rather than from screenshots alone. One-time unlocks carry less expectation of endless new features than a subscription, and later packs can be sold to existing users. The downsides are no steady recurring income, more implementation work than a paid download, and the risk of giving away the core novelty for free so users never upgrade. This fits hobby and one-off apps, content packs, and teams that want faster feedback.

Subscriptions: Recurring revenue rewards ongoing value and can cover high per-user costs. A free tier, trial, or short billing period also lowers the entry barrier. Implementation and maintenance are more complex, the paywall line must be drawn carefully, and retention requires real recurring value. On visionOS that last point is the hardest: a buyer unsure about using the headset regularly will struggle to see recurring value in an app tied to it. Subscriptions fit high-cost apps, and existing iOS or macOS subscription apps that add visionOS as an included platform rather than selling it separately.

What other visionOS apps were doing in March 2024

A March 25, 2024 snapshot shared by Ariel from Appfigures showed native visionOS apps split roughly into thirds: free, paid up-front, and subscriptions or in-app purchases combined. Paid up-front was more common than on iOS, plausibly because indie developers made up a larger share of early visionOS releases.

Among apps exclusive to visionOS, with no iOS or macOS version, the split was sharper: nearly half were paid up-front, about 40% were free, and only around 13% used in-app purchases or subscriptions. That pattern matches the one-time-experience logic above rather than proving it is optimal for every app.

Recommendation and decision checklist

Use this checklist before picking a price or model:

  • Is the value delivered in one session or across months? One session points to paid up-front or a one-time unlock; ongoing value can support a subscription.
  • Do you pay a cost every time an existing user opens the app? If yes, avoid a purely one-time model unless that cost is negligible.
  • Will a free tier reveal the whole novelty? If so, move the distinctive experience behind the paywall or charge up-front.
  • Do you need feedback and downloads more than immediate simplicity? A free tier with a one-time purchase trades extra implementation for a larger learning audience.
  • Can an existing subscription simply include visionOS? That is usually a stronger subscription case than launching a headset-only subscription.

The practical recommendation for a new, headset-only app at this stage is to build small experiences that use the hardware in a way other platforms cannot, sell them as a movie-like one-time experience, and start at a relatively high price while testing alternatives, since early owners were comparatively price-insensitive. A free tier with a one-time purchase is the better variant when learning from users matters most. For discovery, short video demonstrations on social media matter more than store screenshots alone, because people without the headset still watch Vision Pro content and may share a compelling demo.

Frequently asked questions

Why are subscriptions a harder sell on visionOS than one-time payments?

Ads need frequent use from many people, which is hard when the installed base is small and headset sessions may be less frequent than phone sessions. Paid up-front and one-time purchases collect the full value immediately and suit one-off experiences, but provide no repeat revenue. Subscriptions can fund recurring per-user costs, yet buyers must believe they will keep using both the headset and the app.

How should I choose between paid up-front, in-app purchases and subscriptions?

Use paid up-front when you want the simplest release and have no recurring per-user costs. Use a free tier with a one-time in-app purchase when you want more downloads and feedback while still avoiding an ongoing value promise. Reserve subscriptions for apps with ongoing costs or an existing subscription that can simply add visionOS as another platform.