iPad Pro M1
51–60 of 503 posts
Re: iPad Pro M1
#52It'll be interesting to see if iPadOS 15 steps us any closer to laptop/desktop class usage. The biggest thing holding back iPad from being a real laptop replacement for so many is the software. It's also not as simple as porting macOS to iPad. I get Apple's hesitancy from a usability and a product cannibalization standpoint, but it's time they step things forward.
M1 > SwiftUI > MacCatalyst = Write once, run anywhere.
Watching the iPadOS and MacCatalyst APIs mature says different form factors will emphasize certain workflows over others, but overall, feature parity is and will be a priority across the device lineup, iPhone included...
Though it makes me sad... soon after their unified OS is realized, Sherman's coming by with his hammer. It'll be beautiful while it lasts.
Re: iPad Pro M1
#53Re: iPad Pro M1
#54I understand there are more people interested in the use cases apple illustrated in their presentation than software developers who just want to run docker on their ipads so I wont hold my breath.
But I'd love to actually justify the need for an M1 to be in an ipad.
Re: iPad Pro M1
#55Re: iPad Pro M1
#56How long before MacOS and iPadOS have enough feature parity that they get merged?
Probably never. The divergence between macOS and ipadOS is not technical, it's that Apple believes a touch-oriented and a pointer-oriented interface are completely different things.
Re: iPad Pro M1
#57It'll be interesting to see if iPadOS 15 steps us any closer to laptop/desktop class usage. The biggest thing holding back iPad from being a real laptop replacement for so many is the software. It's also not as simple as porting macOS to iPad. I get Apple's hesitancy from a usability and a product cannibalization standpoint, but it's time they step things forward.
As an active user of the Mac. That would not be a step forward. It would be a step backward. There are so many things that are fundamentally impossible on a closed ecosystem like the iPad. For example, Macs still support, even on the M1, installing your own OSes. I don't get why some Apple fans are so interested in destroying a core stable of Apple's userbase.
Of course just saying this out loud sounds ridiculous considering that Apple is Apple but hey, we can dream. :)
Re: iPad Pro M1
#58Earlier quoted context omitted.
Probably never. The divergence between macOS and ipadOS is not technical, it's that Apple believes a touch-oriented and a pointer-oriented interface are completely different things.
With BigSur, users can run ipad and iphone apps natively on an M1 mac. It's not a large stretch to see some overlap between allowing macOS features on a large screen mobile device.
It is in fact a rather large stretch. macOS allowing the larger targets of iPad applications is a rather different proposition than macOS's rather small targets being on touch devices.
Re: iPad Pro M1
#59Re: iPad Pro M1
#60It'll be interesting to see if iPadOS 15 steps us any closer to laptop/desktop class usage. The biggest thing holding back iPad from being a real laptop replacement for so many is the software. It's also not as simple as porting macOS to iPad. I get Apple's hesitancy from a usability and a product cannibalization standpoint, but it's time they step things forward.
For example, I frequently need to save a PDF from my Google Drive app either to my local Files or the Books app. But both those options are just... missing from the iOS share sheet, even though Acrobat is there. So I have to share to Acrobat, then share to Files or Books from within Acrobat. Bizarre.
The problem is some kind of combination of file type plus application -- Gmail will let me share a PDF straight to Files or Books just fine.
Or sometimes when you open a PDF in Books from another app it saves it to Books as a copy... but in other cases it opens it in-place. So you think you copied a bunch of things into Books to read on the airplane... and then they're not there.
The fact that there's never any indication whether something is being copied or not, and that apps that support a filetype are simply arbitrarily missing from some share sheets (but not all), makes iPadOS just a disaster for any serious work that spans multiple apps.