Christina WarrenThe problem with the iPad as as many have pointed out is that the software hampers what it can do unless you’re willing to contort yourself into a very specific workflow. For most casual users those limitations aren’t an issue and the advantages of the form factor outweigh the deficits. But when you charge MBPro money for a device the trade-offs sting. As @jsnell says, the best solution would be to just let us virtualize macOS on an iPad Pro when using it in certain modes https://sixcolors.com/post/2024/05/the-ipad-pro-is-no-longer-the-future-so-whats-next/
John Conway@film_girl @jsnell I don't think that would fix the problem. All the apps need to get on-board with freeing their files too.
@john @jsnell honestly, Apple loves to ignore these kinds of edge cases on the preposition that every app will use only Apple frameworks and APIs so I don’t think it would be a blocker at all. The reality would be that some apps might only work in one mode or the other. And as I said, default to iPadOS. Make that the primary. But for Pro users on a Pro device with connected accessories, allow macOS mode to work.
@film_girl @jsnell Sure…. I'm just not sure how that would work in practice.
For example, how would Procreate handle files spread out in project folders outside its sandbox? Putting MacOS in front of that won't help will it? I mean, I will see the files, but I can't move them because it will break Procreate's expectations/limitations.
I guess I think that any use I'd get out of MacOS would need to be backed up with such fundamental changes to the iOS model, that it might be redundant.
@john @jsnell I mean, virtualization allows pass-through access to network and storage components. So you’d just approve permissions to access stuff stored locally to your iPad. But in the case of Procreate, the default for both Mac and iOS of those is iCloud anyway. And the VM wouldn’t be using a separate storage device. Again, there might be *some* edge cases and limitations but that’s why this would be an option, not the only solution.
@film_girl @jsnell
I'm not sure what you’re saying about VM passthroughs. Permission to access could of course be given, but apps on iOS are designed around a different model, right?
Procreate doesn't store it's files in iCloud, you have to export them do that. I think this has to do with file-size problems. It's kinda disastrous really (they are lucky the painting experience is so good).
@film_girl @jsnell I guess what I'm saying is that if they just give up and give us a normal file system, tell app developers that's the way it is, and provide a syncing API for that filesystem, then that pretty much solves my issues with iPad OS.
Jason Snell@john @film_girl I don't think this is on Apple, the filesystem has been exposed for developers and users on iPad for years now. iCloud or on device. Files app. If you're using an app that doesn't let you save there, that's on the developer.
@jsnell @film_girl Well, one of the flagship Pro apps on iPad lets you export to there, but not save. Maybe it's on Procreate, but I do remember there being some file size problem.
In the end I think this is Apple's fault because they led us down this app-centric path to start with. It was never going to work well for multi-application workflows, but they kept hoping. And here we are 14 years later talking about cramming a whole other OS in!