User story: I want to run macOS apps on iPad Pro. Implementation detail: difficult without significant redesign to run them on iPad OS. Solution: Why can't I have macOS on iPad os? Another implementation challenge: Apple would have to make macOS touch compatible to be consistent and find a way to not frustrate users with apps that are not designed for touch at all.
btw.: Would you mind sharing your survey? You are mentioning it but you are not sharing the details. Makes it hard to judge if it is relevant or not
thing is the UI code is pretty generic and can be re-bound. there's nothing to stop apple doing a shim to essentially migrate macOS UI elements to iPadOS UI on a one for one basis. both have buttons, drop downs, mouse pointer targets, etc. available in the UI kit.
The menu bar? Can trivially be re-displayed in an iPadOS specific UI element. The dock already exists on both platforms, Window management via stage manager already exists on both platforms.
I'm hoping for this and if I was running apple I would be working towards this. Running iPad apps on the Mac is step one, running Mac apps on iPadOS is step two, and sooner or later the platforms will converge and the UI for the app will simply shift to the relevant UI depending on what platform the app runs on.
The hardware is the same. Both platforms have their roots in nextstep, there's no technical reason apple can't do this. Its just a question of the will to do it, and given the hardware advance on the higher end iPads, the commonality with the Mac hardware and the cleanly abstracted UI of native macOS or iPadOS apps I think it is inevitable. I'm just hoping the time is "soon", hopefully iPadOS 18.
As above - I DO NOT WANT macOS on the iPad. I want apps to basically shift UI based on the platform they are running on. As above, there is little technical reason this can't be done, and unlike Windows, as macOS and iPadOS UI are fairly cleanly abstracted from the rest of the application I don't even believe it would be difficult for a company with a fraction of Apple's resources. It's just a case of will to do it.
Microsoft is not in a position to do this with Windows due to the legacy baggage and decades of hacks upon hacks to the core codebase. Just look how it has taken them more than a decade to try and get rid of control panel, and still haven't managed it yet. The code complexity and baggage is why.
As an aside, this is how the vision pro is going to end up with a large number of apps as well. The UI events in the code will simply be re-targeted to Vision Pro UI elements, just like I have proposed above for macOS/iPadOS. Same thing.
Apple have been maintaining a fairly clean code base with clear lines of demarcation in their libraries for decades now - they've been doing so with the long game in mind, and the fruits of their labour in doing so are close to becoming reality. They had the opportunity to start over with nextstep/macOS X once all this was feasible from a performance perspective.
Microsoft on the other hand has been spending far too much effort maintaining legacy compatibility with 35 year old hacks in their platform and as a result do not have this flexibility. Which is why they have tried to force one OS everywhere and we had the whole Windows 8 UI debacle and 3-4 years in there was still no native touch version of office for Windows. There still isn't - if you want a touch friendly version of Office you buy an iPad.