You can not position windows, but if you’re displaying this 3D content in a “window” and a not a volume, why not try a custom ornament? The HIG recommends them for spatially relevant supplementary controls and information.

Do you need to add a collision component to the model entity for the gestures to “contact” it? That was required in pre-Vision RealityKit

Can we dive into UIKit to change the window size dynamically?

Also the problem with just displaying 2D content in a volume is that the ”window grabber bar” moves around the volume and the user could end up looking at the side of the plane and not see anything.

I agree and filed a feedback for this. Why in the world you can set a volume to be 300x300x1 and not a window is beyond me.

Also Filed FB12639395

Did you solve this??

An apple individual on the Slack Q&A today said that only green indications for planes are expected.

I just encountered this on MacOS and not iOS. Did you figure this out?

I think actions from within a view itself should cause a "drill down" / push onto the navigation stack, and It seems SwiftUI is designed to encourage this pattern as well. I have a similar dropdown in my app that shows a settings view, and it does so as a "sheet". This ends up looking fine on both iPhone and iPad, so I've kept it. If you actually want to open a window, you'll need to explore the openWindow utility that's in the swiftUI environment. Opening windows will only work on iPad and Mac, though.

I’ve noticed the same thing. Have you heard from apple about this?

That may not get you all the way there unless you support all file types. Something like the following will only accept images, for example. @Parameter(title: "Image", description: "Image to copy", supportedTypeIdentifiers: ["public.image"], inputConnectionBehavior: .connectToPreviousIntentResult) var file: IntentFile

The food truck sample app includes some sample app intents.

For any one seeing this in the future "Com.image" is not the correct UTType for image. It's "public.image". That did not impact the problem at hand here, though.     @Parameter(title: "Image", description: "Image to copy", supportedTypeIdentifiers: ["public.image"], inputConnectionBehavior: .connectToPreviousIntentResult)

Any good Engineer will tell you the super unsatisfying answer: "It Depends". Getting started with python scripting and other simple coding languages like that? 8GB can be fine. For iOS I find that I'm okay with 16GB. I see developers I follow on Twitter struggling with 16GB and 32GB when they're running one of every kind of simulator at the same time. There is likely some sort of AR/VR development kit on the horizon, and this may be more demanding than traditional iOS/Mac development. We won't know any details about that until Apple wants us to, though.