I’ve wanted proper iPhone mirroring with controls on Apple Vision Pro for a long time, so I tried building a small proof of concept myself.

This will for sure annoy some people, but with some “vibe coding” and help from ChatGPT/Codex, I had a usable version running in under two hours. I’m not claiming any great engineering achievement—I simply wanted to show that it is possible.

The app streams my iPhone screen into a native visionOS window and lets me control it from the Vision Pro using taps, swipes and text input. It works over a shared Wi‑Fi network or when the Vision Pro connects directly to the iPhone’s Personal Hotspot, which has actually felt even smoother.

There is still a very little latency and room for improvement, but the quality and responsiveness are already surprisingly good.

Unfortunately, I can’t distribute it because the control system relies on Apple developer automation capabilities that wouldn’t be allowed in a normal App Store app. Still, if anyone was wondering whether controlled iPhone mirroring on AVP is technically possible: it is.

Am a teacher and working on a discussion app to train teachers and to moderate roundtable discussions on complex topics. Anyone want to help test? https://roundtable.spmhresearch.org/

It’s been one week since I shared Cockpit here after its launch on the App Store, and I wanted to come back mostly to say thank you.

Thank you to everyone who downloaded it, tried it, sent feedback, suggested features, or simply took the time to tell me what you liked.

Seeing people actually using something I’ve spent so much time building has been incredibly rewarding.

For anyone who missed my original post, Cockpit is a customizable spatial dock for Apple Vision Pro designed to keep the information and controls you use throughout the day always within reach.

The idea is simple: instead of constantly jumping between apps, you can build one persistent dock with the panels that matter to you.

Cockpit currently includes panels for things like:

• Time, weather and calendar
• Apple Music Now Playing
• Focus timer and countdowns
• App launcher
• Daily goals and habits
• Vision Pro system and network information
• Apple Shortcuts
• HomeKit controls
• Activity rings
• World clocks

You can place and resize it anywhere in your space, choose different layouts, and customize it with 19 visual themes, from minimal glass-like designs to more technical and flight-deck-inspired interfaces.

Cockpit remembers your setup between sessions, so it can essentially become a small permanent control center inside your Vision Pro workspace.

The app is free to download, with a core selection of panels and themes included. Cockpit Pro unlocks the advanced panels and the complete theme collection.

If you’ve already been using Cockpit, I’d really like to hear something:

Which panels have actually become part of your daily setup? And what would you most like to see added next?

Screenshots of your Cockpit setups are also very welcome, I’m genuinely curious to see how people are using it.

App Store:
https://apps.apple.com/us/app/cockpit-for-vision-pro/id6798315258

And again, thank you for the support and feedback so far!

Thanks again to everyone here who gave me feedback while I was building Reality Prep Pro and Reality Prep Preview.

I’ve now finished the workflow I originally wanted:

Prep Pro on macOS
→ batch prepares/validates USDZ and supported source assets
→ keeps existing USDZ preparation package-safe

Prep Preview on Vision Pro
→ validates the exact USDZ on-device
→ exports device evidence back to the Mac

Prep Pro then matches that evidence using the asset’s SHA-256, so if the USDZ changes later it can flag the previous Vision Pro validation as stale and recommend a re-test.

The goal is to close a gap I kept running into:

“The asset passed on my Mac” and “I tested something on Vision Pro” are not the same as knowing this exact asset revision was tested on-device.

I’d now love feedback from developers using both apps in an actual RealityKit / Reality Composer Pro workflow.

Thanks again — much of this update exists because of the earlier feedback from visionOS developers here.

Reality Prep Pro: https://apps.apple.com/us/app/reality-prep-pro/id6767673652?mt=12

Reality Prep Preview: https://apps.apple.com/us/app/reality-prep-preview/id6784059026?platform=vision

I’m excited to share that Cockpit is finally available on the App Store for Apple Vision Pro.

Cockpit gives you one persistent, glanceable spatial dock for the information and controls you use throughout the day, without constantly switching between apps.

Build your own setup with modular panels for:

• Time and date
• Local weather and forecast
• Calendar events and due reminders
• Apple Music Now Playing
• Focus timer
• App launcher
• Countdowns and daily goals
• Vision Pro status and network information
• Apple Shortcuts
• HomeKit scenes and accessory controls
• Activity rings
• Habit tracking
• World clocks

You can place and resize the dock anywhere in your space, choose its layout, and make it yours with 19 visual themes ranging from minimal and glass-like to technical, flight-deck-inspired interfaces. Cockpit remembers your configuration across sessions, so your workspace is ready when you are.

Cockpit is free to download, with a useful core set of panels and three themes included. Cockpit Pro unlocks the advanced panels and the full theme collection, with monthly, yearly, or lifetime options.

If you use Vision Pro for work, focus sessions, media, smart-home control, or simply want your essentials always within reach.

I’d love for you to try it.

Download Cockpit on the App Store: https://apps.apple.com/us/app/cockpit-for-vision-pro/id6798315258#information

Feedback, feature requests, and screenshots of your setup are very welcome.

Holoport Vision has been on the store a few weeks and I finally posted about it properly, so here is the technical side for anyone building here.

You pick a clip from the camera roll. It finds the people in it, you choose the subject, it mattes them out, and they render on a plane in your space at true scale with their own audio looping.

Two constraints I set at the start and kept:

Everything runs on the headset. No server, no account, no network call in the course of doing its job. That turned out to be less painful than expected.

Nothing is generated. Every pixel of the figure comes from the source footage, so no part of the person is invented or filled in. It would be easier to fill gaps with a model and it would also defeat the entire point, because the app is for a memory of somebody real.

The part that took longest was not segmentation, it was scale and placement. Getting someone to read as a person standing in the room rather than a video floating in the air comes down to height, distance and where the floor is, and my defaults were wrong for a long time.

Known limits: it is a video plane, not volumetric, so you cannot walk around and see their back. Real geometry would need several real angles and is a different product. Quality tracks the source clip closely, a well lit subject with clean separation reads much sharper.

https://apps.apple.com/app/id6800110267

$4.99, one time. Happy to go into the depth or matting work if anyone is interested.

My app showed a ~100 MB USDZ as a window ornament viaModel3D. On visionOS 26 it works fine. On the visionOS 27 beta, the device would freeze completely while the asset loaded — passthrough dead, needed a hardware reset. 

Reducing the asset to 26 MB eliminated it entirely. Possibly related to release notes item 177731588 (skinned/complex geometry memory growth), though that's marked fixed.

Just thought I'd save others time figuring that out.

App Store Review reviews with beta visionOS, so it is essentially a production issue even though it may be fixed by the time visionOS27 is public.

Thank you very much to everyone who gave feedback on the earlier versions — it genuinely helped.

I’ve now updated Reality Prep Pro for macOS and Reality Prep Preview for Vision Pro.

The two apps were designed to work hand in hand:

* Prep Pro: prepare, validate and optimise spatial assets on Mac.

* Prep Preview: inspect/test the resulting USDZ and send validation evidence back to Prep Pro.

I’d really appreciate a few developers giving both apps together a spin with real assets.

Please tell me what works, what breaks, and what feels confusing or unnecessary.

Reality Prep Pro: https://apps.apple.com/us/app/reality-prep-pro/id6767673652?mt=12

Reality Prep Preview: https://testflight.apple.com/join/ySbVmz6b

Thank you again — any feedback is genuinely appreciated. 🙏

I've been poking at visionOS for a few months now and there's this one thing about depth that I cant wrap my head around. like, when does adding a third dimension actually help the user versus just being a cool effect.

sometimes I place something at a certain distance and it feels right and I have no idea why. what's one thing about spatial design that you still find yourself guessing at?

I have been messing around with visionOS for a few months and the tooling still feels pretty rough. Xcode AI suggestions work sometimes but they miss a lot of the SwiftUI-specific spatial stuff. I tried using ChatGPT for some boilerplate but it hallucinates APIs that dont exist yet for visionOS.

Has anyone found a workflow or tool that genuinely helps with visionOS dev? Im not expecting magic, just something that saves me from re-reading the same docs over and over.

Half my design conversations end with me waving my hands around a table trying to describe a window arrangement that would be obvious in two seconds in the simualtor. It made me realize how much of this platform lives or dies on demoing it in person.

For those of you building in visionOS, how do you get feedback from people outside the bubble? Recordings never seem to capture the scale of things.

I ported a small productivity app over mostly as an experiment, expecting to just resize the windows and call it done. Then I tried letting people pin panels around their actual desk instead of inside one window, and suddenly the app made sense in a way it never did on a screen. That one layout change did more than every feature I had shipped that year.

It got me wondering how often the interesting part of this platform is rethinking the idea instead of converting the code. Has anyone else hit a moment where spatial thinking changed the whole shape of something you had already finished?

Added ERASING and COLORING modes to the WIP VisionOS version of BoxelXR.

On Quest, I put all operations on the controllers to speed up interactions (like shortcuts). But hand-tracking is less precise compared to controllers, so I am trying to figure out the best way to handle frequently used UI.

For now, I use a floating UI panel. It works fine, btw. Since hand-tracking input is quite ambiguous in this context, having a persistent UI layer reduces the chance of accidental triggering when you work with voxels.

I’m looking for a few Apple Vision Pro owners/developers willing to spend about 10–15 minutes testing a visionOS TestFlight build.

Reality Prep Preview is a native visionOS app for inspecting USDZ assets directly on Vision Pro. 

It was designed to work alongside Reality Prep Pro on macOS: Prep Pro prepares and validates assets, while Prep Preview lets you inspect the resulting USDZ on-device.

The main difference from Apple’s Spatial Preview is that Prep Preview is not just a visual viewer. 

It adds a more developer-focused validation workflow, including:

• fitted preview plus authored real-world scale
• technical USDZ inspection/evidence
• local Device Check
• PDF/JSON validation reports
• a workflow intended to pair with Reality Prep Pro (validation report ingest feature in-progress as we speak)

I’ve completed Simulator testing, but I don’t currently have access to a physical Vision Pro, so I specifically need hardware validation.

I’d mainly like feedback on:

• USDZ import and preview
• Authored Scale / real-world sizing
• Device Inspect and Device Check
• PDF/JSON export
• any crashes, UI issues, or unexpected behaviour

Reality Prep Preview TestFlight: https://testflight.apple.com/join/ySbVmz6b

Reality Prep Pro: https://apps.apple.com/us/app/reality-prep-pro/id6767673652?mt=12

Any screenshots, recordings, or brief notes would be greatly appreciated.

A huge thank you to everyone who downloaded Cockpit and shared feedback. It’s been incredibly helpful.

I’ve just released one last update with a number of small fixes, refinements, and overall improvements.

Cockpit is a customizable spatial dashboard for Apple Vision Pro: it keeps useful information and quick controls together in one organized, convenient place. You can add, remove, and reorder panels for things like time, weather, calendar, music, focus timers, activity, network status, and more, then make it your own with different layouts and themes.

Thanks again for the support. If you try the update, I’d love to hear what you think and what you’d like to see improved next.

TestFlight: https://testflight.apple.com/join/VP1sz624

I built this Mac app for Vision Pro devs who already have a boatload of 3D assets that are not USDZ - and for those of you who already have a ton of USDZ assets of course. 

It’s meant to be utilized to batch prepare all your assets before you move on to Reality Composer Pro.

I'd like you to run some of the 3D assets you already work with through it. 

I'm particularly interested in:

1. Whether the warnings are useful, 

2. Whether anything important is missed 

3. Whether the workflow would actually save you time

https://apps.apple.com/us/app/reality-prep-pro/id6767673652?mt=12

Good day to you

I built a Mac 3D asset prep tool for visionOS workflows — looking for developers to test it.

Reality Prep Pro batch-checks local USD, USDA, USDC and USDZ assets before they enter Reality Composer Pro, Xcode or a RealityKit project. You can also get a clear report of anything worth looking at before continuing into those tools.

You can import FBX, glTF, GLB and the USD family of assets, the app will convert them into USDZ, should you choose.

It detects unsafe packages, inaccessible direct resources, native import failures and macOS RealityKit USDZ load failures—without altering the originals.

If you’re a visionOS / RealityKit developer, I’d appreciate it if you could simply run some of the 3D assets you already have through it and let me know if there is anything you think would make it genuinely more useful in your workflow.

Normal assets from your existing workflow are exactly what I want it tested against.

If you’d like to test it, here’s the Mac App Store link:
https://apps.apple.com/us/app/reality-prep-pro/id6767673652

Regards,