Haven't seen it explicitly called out, but if you wanna write a full-featured visionOS app with UIKit & Objective-C, it all still works natively and takes full advantage of the system. You need to use a few lines of Swift/SwiftUI if you want to present ornaments (floating toolbars), or if you want to do anything 3D like view transforms or integrating 3D content. And if you want to make a volumetric or immersive (VR) app, you need to move to the SwiftUI app lifecycle. But ObjC codebases are a go
@stroughtonsmith While technical reasons probably mean it will work at launch, don’t assume that it will. Us old Mac heads remember when Apple shipped 64-bit Carbon libraries in the beta builds, then removed them shortly before launch. https://daringfireball.net/2008/04/64000_question h/t @gruber
Daring Fireball: The $64,000 Question

@smitty825 @gruber difference is most of the OS is written with it, and it's essential to providing compatibility with existing iOS apps. This isn't going away any time soon, especially as it's made the jump to yet another OS