You’re missing the forest from the trees - it’s not one device it’s one user interaction layer. Drag and drop from real life to AR, to Illustrator, to printed d

You’re missing the forest from the trees - it’s not one device it’s one user interaction layer. Drag and drop from real life to AR, to Illustrator, to printed document should follow one framework. We’ve entered into a realm where context dictates the task for the desired computing aims. The paradigms for user interaction change if you’re on a bus, at a desk, walking in the park. A unified abstraction for how to achieve user intent may be one device, but for certain a continuous ecosystem requires one language and one API paradigm to achieve user aims. That said, there are good ways of going about it (MacCatalyst) and bad (SwiftUI) - and I say this in light of whatever VR/AR is coming. I know a guy working on this for AR and thought he had 0 shot on earth, but seeing Apple go for SwiftUI greatly increases his chances.