The App Store on Apple Vision Pro: what spatial computing means for ASO

Apple has sold an estimated 600,000 to 1 million Vision Pros in two years, and its October 2025 M5 refresh "may have had little impact on struggling Vision Pro sales" (9to5Mac, 2026). By almost any commercial yardstick, the device underperformed. So why write about its App Store at all?

Because that same store lists only about 2,000 native apps and shows no top charts — which quietly makes it the least competitive discovery surface Apple has ever shipped. Founders keep asking the wrong question. "Is the Vision Pro dead?" is a hardware question. The ASO question is sharper: is a near-empty, search-dominant store worth a listing, and for which apps? This guide gives you the real market numbers, exactly how discovery and metadata differ from iOS, the low-competition opportunity and its limits, and a clear build-native, ship-compatible, or wait decision at the end.

How big is the Vision Pro market really?

Small, and not growing quickly. As of 2026, analyst estimates put lifetime Vision Pro sales at roughly 600,000 to 1 million units, with IDC cited at just ~45,000 units in the 2025 holiday quarter — the quarter that included the M5 launch (9to5Mac, M5 Vision Pro launch report, 2026). At a $3,499 price with a heavy enterprise skew, this is a niche install base, not a mass market. Honest ASO strategy starts by saying so out loud.

The M5 model — released October 22, 2025 with a 120Hz display, roughly 10% more rendered pixels, and a more comfortable Dual Knit Band — kept the same $3,499 price and did not move the needle (Apple Newsroom, 2025). The device is now sold in 12 countries and regions. So how can "flop" and "opportunity" both be true? Simple: the opportunity isn't the audience size — it's the denominator. When almost no one builds apps for a platform, the few who do face almost no competition.

Keep that context in your pocket for the rest of this guide. Every recommendation below is calibrated to the reality that you're optimizing for a small, largely professional audience — which changes what "worth it" means. For the wider platform picture, see how Apple's roadmap changes shaped ASO.

Why is app discovery different on Vision Pro?

Because the browse layer is gone. As of 2026, the visionOS App Store surfaces no top charts and no curated category browse the way the iOS store does — discovery runs almost entirely through search (SplitMetrics, visionOS ASO Guide; Yodel Mobile, 2026). That single difference makes the keyword and search layer more decisive on visionOS than on iOS, not less. There's no chart to climb your way onto — you rank in search, or you're invisible.

And people search in ways a keyboard-first strategy never anticipated. visionOS offers three inputs: air typing on a floating keyboard with no haptic feedback, look-and-pinch letter selection, and voice dictation — with voice reported as the fastest, most convenient method (Yodel Mobile, App Store Optimization for Apple Vision Pro, 2026). Would you type letter by letter by pinching the air, or just say what you want? Exactly. So the winning metadata reads like spoken language. That means natural phrasing — the kind that survives accents, slang, and the dictation errors that mangle invented brand names and acronyms.

One practical note: with no charts and thin editorial surfacing, external catalogs like vision.directory have sprung up to fill the discovery gap, and developers report the store's own analytics and attribution as "sub-standard" (Yodel Mobile, 2026). Measure conservatively, and lean on your App Store keyword research discipline — it carries directly across, with the emphasis shifted toward spoken queries.

What are the metadata rules for the visionOS App Store?

Familiar fields, new emphasis, one hard gate. The App Store Connect basics carry over — a 30-character app name and 30-character subtitle, plus the standard keyword field, promotional text, and description — but two things change the game. Discovery leans on that keyword and search layer harder because there's no browse, and Apple requires app motion information in the listing as a safety disclosure for apps with movement, quick turns, or camera-perspective changes (SplitMetrics, 2026; Yodel Mobile, 2026).

Name and subtitle discipline matters more when they're doing more of the ranking work. Apple's own guidance favors a concise, informative paragraph followed by a short list of features that are unique to the spatial experience — clarity of function over heavy branding. visionOS also adds spatial-specific privacy data groupings such as "Surroundings" and "Body," which you'll need to represent honestly in your listing. Here's how the two stores line up on the differences that actually affect your ASO work.

The standard iOS keyword-field and promotional-text limits still apply — the difference is where you spend the effort, not new fields to learn. Before you publish, count your metadata characters and pack the keyword field around spoken terms, then preview the listing so the name and subtitle read cleanly at a glance.

How should you design spatial screenshots and previews?

Authentically, and video-first. As of 2026, Apple wants screenshots screen-grabbed or recorded from an actual Vision Pro or an accurate simulation, at 3840×2160, with hands and gestures shown only when they clarify the interaction — not staged marketing renders (SplitMetrics, 2026). And because the store is video-forward, an app preview of about 30 seconds performs best and does more conversion work than any static shot. One more trap: icons render round on visionOS, so anything you tuck into the corners gets clipped.

Why does "functional over branded" win here specifically? Because the user is judging an experience they can't yet feel. On a phone, a glossy hero shot can carry a listing; in a headset, the buyer wants to see what the app actually does in their space, so a real capture of the interaction beats a polished abstraction every time. That's a different instinct from flat-screen creative, though the underlying craft — sequencing, captions, a strong first frame — is the same discipline as designing and adapting App Store screenshots anywhere.

The sting in the tail is that A/B testing — Apple's Product Page Optimization on iOS — isn't available on the visionOS store yet (Yodel Mobile, 2026). You can't experiment your way to a winning screenshot order the way you can on iOS. So get the first version right by borrowing your iOS learnings, and treat the same principles that drive app conversion rate — clarity, benefit-first framing, social proof — as your starting hypothesis rather than something you'll tune later.

Why is visionOS the least competitive ASO surface in the ecosystem?

Because the math is inverted. As of 2026, the visionOS store lists roughly 2,000 native apps, up from more than 600 at the February 2024 launch. Set that against 1.5 million-plus compatible iOS and iPadOS apps that merely run on the device (Apple Newsroom, 2024–26). Compatible apps don't compete for spatial intent — someone searching the visionOS store wants a spatial experience. So a single well-named native app can own a search term in a category that would take months of contested work on the ~1.9-million-app iOS store.

In a search-dominant store with almost no competitors, first-mover metadata is a genuine land-grab. But be honest about the catch: a term you own reaches a tiny audience. The opportunity is real and it's bounded. It pays off for apps whose value is spatial — 3D and CAD, immersive media, productivity you arrange in space, training and enterprise simulation — and it's mostly a distraction for everyone else. Deciding where your app sits is a strategy question, which is exactly what an effective ASO strategy is for, and where the right ASO partner earns their keep on a platform bet.

Build native, ship compatible, or wait?

For most apps in 2026, ship a compatible iPad or iPhone build and optimize the listing for voice search first. It costs almost nothing — you're already one of the 1.5 million-plus compatible apps that run on the headset (Apple, 2024–26) — and it captures the spatial audience without a native rebuild. Reserve a full native visionOS build for apps whose core value is genuinely spatial, where the low-competition land-grab actually pays. Wait only if your app has no spatial dimension and no enterprise angle; there's no ASO reason to force it.

The framework fits on a napkin. Does your app's value depend on space, depth, or immersion? If yes, and you have the team capacity, build native and grab the uncontested search terms now. Is there enterprise or training demand — the segment that actually bought most of the headsets? That tilts the call toward native even at low consumer volume. Neither? Ship the compatible build, optimize for voice, and spend the saved effort where your users already are. Even the compatible path isn't a throwaway — it's cheap R&D that teaches you voice-search behavior before it matters everywhere else.

What spatial ASO signals for the rest of the App Store

The reason to care about a niche store is that it's a preview. visionOS already runs voice-first search, mandatory ~30-second video previews, and authentic-over-staged creative. Those are the same three directions the broader App Store is drifting, as Apple leans into search suggestions, video, and increasingly AI-assisted, natural-language discovery (synthesis of SplitMetrics and Yodel Mobile guidance, 2026). Teams that learn voice-optimized metadata and video-first creative on visionOS now are rehearsing the iOS playbook of a few years out.

There's a caveat worth stating plainly: Apple may de-prioritize the Vision Pro hardware while keeping the spatial platform alive through cheaper devices down the line. So optimize for the model, not the gadget. The voice-first, natural-language shift is the through-line connecting spatial search to AI-assisted app discovery across every surface — and it's the same reason the gap between the two stores keeps evolving, which we track in the ASO differences between the App Store and Google Play. The headset is the experiment. The discovery model is the destination.

The bottom line

Vision Pro ASO is a paradox worth understanding: the least competitive App Store surface Apple ships sits on top of one of its least successful products. Both facts are real, and the strategy follows from holding them together:

• The market: an estimated 600K–1M lifetime devices, enterprise-leaning — a niche audience, not a growth channel.
• The opening: ~2,000 native apps and no top charts mean search terms are winnable now in a way iOS hasn't allowed in a decade.
• The rules: 30-char name and subtitle, a required motion disclosure, authentic 3840×2160 screenshots, a ~30-second preview, round icons, and no A/B testing yet.
• The discovery: search- and voice-first — write metadata the way people speak, not the way they type.
• The decision: build native only if your value is spatial; otherwise ship compatible, optimize for voice, and treat it as cheap rehearsal for where all ASO is heading.

Trying to decide whether spatial belongs on your roadmap this year? Book a free 30-minute call and we'll pressure-test the build, ship, or wait call against your app, your category, and your real growth priorities.