What is new in visionOS 26.5 beta 3 for SwiftUI developers?

visionOS 26.5 beta 3 shipped April 20, 2026 with stabilized SpatialSceneContent API for multi-scene coordination, persistent volumetric windows that survive sessions, improved RoomCapture with faster scan times, shared spatial sessions letting two Vision Pro users see shared volumetric objects without a server, better Mac Virtual Display coexistence, AppKit interop improvements for Mac Catalyst apps, and Liquid Glass material propagation to ornaments and toolbars. Mid-cycle release but notable for API parity work.

Should indie iOS developers ship to Vision Pro in 2026?

Yes if you already have a polished SwiftUI iOS or iPadOS app in one of five works-well categories (productivity, content consumption, meditation/focus, design/creativity, media/entertainment) and it fits in 30-80 hours of porting. Revenue is 1-15 percent of iPhone version typically ($100-$3000 per month for featured apps) but Apple featuring potential and positioning value make it worthwhile. Skip if your app is social, messaging, navigation, camera-first, or transactional, or if you are pre-launch on iOS.

How long does it take to port a SwiftUI iOS app to visionOS?

Typically 30-80 hours for a well-structured SwiftUI app (MVVM or clean architecture). Add visionOS target in Xcode (1 hour), fix iOS-only modifier compile errors (5-10 hours), redesign primary scene for windowing (5-15 hours), replace touch-first interactions with eye-and-pinch patterns (10-20 hours), add ornaments for toolbar equivalents (5 hours), add 1-2 volumetric touches for native feel (5-20 hours), test on real hardware (5-10 hours). Apps with heavy UIKit or camera features take longer.

What is the actual revenue ceiling for an indie visionOS app in 2026?

For polished visionOS ports featured by Apple, roughly $500-$3000 per month (5-15 percent of iPhone version). For polished ports not featured, $100-$500 per month (1-5 percent of iPhone version). For direct iOS-to-Compatible-Apps ports without visionOS polish, under $100 per month. For novel spatial-first apps, $200-$5000 per month depending on category. Vision Pro install base is roughly 800K cumulative units and 300-400K daily actives in April 2026.

Which app categories work best on Vision Pro in 2026?

Five categories: productivity (task, calendar, notes) because multiple floating windows match power-user workflows; content consumption (reading, PDF, ebooks) with large virtual canvas and focus mode; meditation, focus, and ambient apps with spatial audio and immersive environments; design and creativity with 3D canvas and spatial manipulation; media and entertainment with cinema-style immersive viewing. Social, messaging, navigation, camera-first, and transactional apps do not work well on Vision Pro and should not be ported.

What monetization works for indie visionOS apps?

Four strategies: Universal Purchase pricing where iOS and visionOS bundle into a higher premium price (Vision Pro users skew affluent), exclusive visionOS features behind existing subscription (spatial workspace or immersive mode as subscription perk), paid-app pricing instead of freemium (Vision Pro users convert better on paid apps), and featuring-driven launches timed with an iOS update for cross-platform Apple editorial coverage. Direct visionOS-only IAP at indie scale rarely sustains a standalone business.

visionOS 26.5 Beta 3 for Indie Developers: What to Ship for Vision Pro in 2026

Q: Does The Swift Kit support visionOS?

Yes. The Swift Kit ships with a visionOS target enabled out of the box. Shared SwiftUI views adapt automatically between iOS, iPadOS, and visionOS (ornaments appear on Vision Pro, toolbar on iPad, tab bar on iPhone). Paywall and RevenueCat integration work cross-platform via Universal Purchase. Foundation Models integration runs on Vision Pro with Apple Silicon M2 and newer chips. Port your iOS app in 30-80 hours instead of starting from scratch.

Apple shipped visionOS 26.5 developer beta 3 on April 20, 2026, the same day Tim Cook announced his transition to Executive Chairman. The release is mid-cycle but notable for indie developers because it finalizes the new spatial scenes API, lands volumetric window improvements, and signals Apple's continued investment in Vision Pro under the incoming Ternus era. This post is the honest indie developer lens on what visionOS 26.5 actually delivers, the minimum-effort port path, and whether shipping to Vision Pro makes business sense in April 2026.

Short version: for SwiftUI-first indie developers with an existing iOS or iPadOS app, porting to visionOS costs 30-80 hours and the revenue ceiling is still low (roughly $50-$3000 per month per indie app average). Worth doing if your app has natural spatial affordances (productivity, content consumption, focus tools, art/design, meditation). Not worth it if your app is pure forms-over-data unless you want the Apple featuring.

What's new in visionOS 26.5 beta 3

Apple's release notes and the community's beta coverage (MacDailyNews and AppleWorld Today both covered the April 20 drop) highlight:

Stabilized spatial scenes API. The SpatialSceneContentcontainer reached API parity with WindowGroup. Now supports transitions, lifecycle events, and multi-scene coordination.
Volumetric window improvements. Volumetric windows can now be persistent across sessions, resize more predictably, and support the new clipping and shadow APIs.
RoomCapture improvements. Better surface detection, faster scan times, support for complex geometries like furniture.
Shared spatial sessions. Two Vision Pro users in the same room can now see shared volumetric objects via low-latency peer-to-peer with no server.
Better Mac Virtual Display. Developers can now test visionOS apps while simultaneously using a Mac Virtual Display on the same Vision Pro, cutting context-switch friction.
AppKit interop improvements. For devs bringing Mac Catalyst apps, AppKit views now render more faithfully in visionOS windows.
Liquid Glass propagation. visionOS windows now pick up the iOS 26 Liquid Glass material fully, including on ornaments and toolbars.

The Vision Pro install base reality (April 2026)

Be honest about the market size. Apple has not published official Vision Pro unit sales but third-party estimates (IDC, Counterpoint) suggest cumulative sales have reached roughly 800K units by April 2026, with daily active users likely in the 300-400K range. Compared to 200 million iPhone daily actives, this is a niche platform.

What that means in practice for revenue:

App quality tier	Typical monthly Vision Pro revenue (April 2026)	Compared to iPhone version
Polished port, featured by Apple	$500-$3,000	5-15% of iPhone version
Polished port, not featured	$100-$500	1-5% of iPhone version
Direct iOS port via Compatible Apps	$20-$100	<1% of iPhone version
Novel spatial-first app	$200-$5,000	N/A (no iPhone version)

The numbers say: direct revenue from Vision Pro is rarely a sustainable standalone business. What it is good for: Apple featuring placements, press coverage, and positioning as an early-mover when the platform grows.

The minimum-effort port path

If your SwiftUI iOS app is reasonably structured (MVVM or clean architecture), the minimum- effort visionOS port is 30-80 hours of real work. Here is the path.

Add visionOS to your Xcode targets. Project editor, add destination visionOS. Xcode 26 handles most of the build-setting conversion.
Run, see what breaks. Most SwiftUI code works unchanged. Modifiers that are iOS-only (like .navigationBarTitleDisplayMode) compile-error; replace with visionOS equivalents.
Redesign the primary scene for windowing. Vision Pro expects floating windows, not full-screen views. Wrap your root view in a WindowGroup with a reasonable default size (600x900 is a good starting point for content apps).
Replace touch-first interactions with eye-and-pinch. visionOS defaults hover feedback for most standard controls. Custom gestures often need adjustment.
Add ornaments for toolbar equivalents. visionOS toolbars render as ornaments outside the window frame. Use .ornament modifier for primary actions.
Pick spatial touches. Optional but high-leverage: add one or two volumetric elements (a 3D icon, a spatial card) so the app feels visionOS-native rather than a resized iPad app.
Test on hardware. Simulator is inadequate for Vision Pro; rent one for a weekend or use TestFlight if you have Apple Developer access.

Five app categories that work on Vision Pro

Category	Why it works	Example indie apps
Productivity (task, calendar, notes)	Multiple floating windows = power-user dream	Things, Noteplan, OmniFocus
Content consumption (reading, PDF, ebooks)	Immersive focus, large virtual canvas	Kindle, GoodLinks, Pocket
Meditation, focus, ambient	Spatial audio + environments = flagship use case	Calm, Headspace, Endel
Design and creativity	3D canvas, spatial manipulation	Procreate, Figma, Pixelmator
Media and entertainment	Cinema-style immersive viewing	Apple TV, Disney+, MLB app

Five app categories that do NOT work well on Vision Pro

Social networks. Not enough users on Vision Pro yet for social UX to feel useful.
Messaging. Phone is better at replying quickly.
Navigation and maps. Wearing Vision Pro while traveling is impractical.
Camera-first apps (photo editing, AR overlays). Vision Pro passthrough camera is not directly accessible, breaks most camera-first apps.
Transactional utilities (banking, shopping). Users default to phone for quick transactions. Vision Pro adds friction.

Monetization strategies that actually work

Given the small install base, four strategies indie developers have used to make visionOS worthwhile:

Universal Purchase premium pricing. Ship the iOS + visionOS combo as one purchase, price higher than iOS-only competitors. Vision Pro users skew affluent and pay premium prices.
Exclusive visionOS features behind existing subscription. If your iOS app already has a subscription, add a visionOS-specific feature (spatial workspace, immersive mode) as a subscription perk. No new SKU; just value for existing subscribers.
Paid app, not free-with-IAP. Vision Pro users convert better on paid apps than on freemium IAP. Consider launching the visionOS version as a $4.99 paid app even if iOS is free.
Featuring-driven launch. Time your visionOS launch with an iOS version update so Apple can feature both. Apple editorial actively looks for Vision Pro content.

Decision framework: should you ship?

A practical answer based on your situation.

You are a solo indie with an iOS app already live. Ship visionOS port if your app fits one of the five works-well categories above. 30-80 hours of work for 1-5 percent incremental revenue plus Apple featuring potential. Yes.
You are planning a new indie app from scratch. Build iOS first. Vision Pro should be a post-v1 addition, not a from-scratch target unless you have a specific spatial-first concept.
You have a spatial-first concept (immersive meditation, 3D modeling, spatial productivity). Vision Pro native is the right launch target. Accept that iOS port might never happen because the UX is fundamentally different.
Your app is in a not-works-well category (social, messaging, navigation, camera, transactional). Skip Vision Pro. Save the 50 hours for iOS improvements.

Ternus era outlook for Vision Pro

John Ternus, who takes over as Apple CEO on September 1, 2026, is publicly bullish on Vision Pro. His public comments during the A/B chip launches repeatedly mentioned spatial computing. Likely implications for indie visionOS developers:

Continued hardware investment (cheaper variant plausible by late 2026 or 2027).
Continued featured-app placements for quality visionOS-native apps.
Possible expansion of visionOS to other devices (spatial content on Mac, iPhone with special viewers).
More visionOS-focused WWDC sessions and dev labs.

None of this makes visionOS a sustainable standalone indie business in 2026. But it does suggest the platform is worth shipping to for indies who can do so efficiently.

Pre-submission checklist for visionOS apps

All target-specific build settings correct for visionOS 26 minimum.
App icon includes the 3D three-layer version Vision Pro requires.
Window default size is reasonable (not a 320x480 iPhone-legacy size).
At least one ornament for primary app actions.
Hover feedback works on all tappable surfaces (automatic for standard controls).
No deprecated iOS-only APIs like .navigationBarTitleDisplayMode.
Tested on real hardware at least once before submission.
Screenshots taken on visionOS simulator (1800x1600 with glass background).
App Store description updated to mention spatial features if applicable.

What The Swift Kit ships for visionOS

The Swift Kit ships with a visionOS target enabled out of the box. The shared SwiftUI views adapt automatically between iOS, iPadOS, and visionOS (ornaments appear on Vision Pro, toolbar on iPad, tab bar on iPhone). Paywall and RevenueCat integration work cross-platform via Universal Purchase. Foundation Models integration runs on Vision Pro with Apple Silicon M2 and newer.

$99 one-time, unlimited commercial projects. See every integration on the features page or jump to pricing.

Final recommendation

Ship to Vision Pro if you are already shipping a polished SwiftUI iOS or iPadOS app in one of the five works-well categories. The 30-80 hour port cost is reasonable for Apple featuring potential, Universal Purchase upside, and position for the platform's long-term growth. Skip if your app is in a not-works-well category or you are pre-launch on iOS. The Ternus-era outlook for Vision Pro is bullish enough to make the bet worthwhile for indies who can do it efficiently.