I completed this column a few days back, however the response to WWDC from the Apple community continues to evolve, and with it, so too have my observations. As an avid iPad Pro user, for whom this is my principal device, I want to concentrate specifically on the user community’s response to iPadOS 15.
Following WWDC, there were three types of bearish responses to iPadOS 15. One was disappointment commingled with optimism about the future, and a ‘buy’ recommendation for the M1 iPad Pro. The second was an angry denunciation of largely ‘cosmetic’ changes to iPadOS, accusing Apple of intentionally holding back the iPad Pro, with a recommendation of ‘hold’ if you already have any iPad from 2018 forward. The third was an apoplectic response, accusing Apple of outright betrayal, having built up expectations, and a recommendation that people return their M1 iPad Pro, and use MacBooks to get ‘real work’ done.
iPad Pro Popular Gripes
Here are five complaints amongst these unhappy iPad Pro users:
- The file system was not fixed, lacking the ease of use of the macOS file system, including naming, adding or modifying folders.
- macOS ‘pro’ apps, like Logic Pro, were not announced.
- The RAM specs on the M1 are not being tapped, since all current iPadOS – compatible apps are capped at 5GB, and no popular ‘pro’ apps were announced.
- Swift Playgrounds is not a serious developing tool, so one still cannot develop real apps on the iPad Pro (see Charlotte Henry’s piece from 16 June for a fuller breakdown).
- Apple did not put macOS on the M1 iPad Pro, thereby enabling a user to purchase only one device and have a true desktop experience.
Let’s Review These Objections.
#1, true, the file system does not work like macOS, nor does iPadOS permit any way to format the hard drive. However, there are multiple file options on iPadOS, including Dropbox, OneDrive, Google and others, as well as on the iPad itself, not to mention using Airdrop to nearby devices. Another part of this is the inability to format attached Thunderbolt drives, many of which are not formatted for the iPad and therefore do not show up when attached via Thunderbolt. All valid criticisms that Apple can and needs to change.
As for #2, if the 2021 iPad Pro, with its M1 processor and 8-16 GB RAM can run (in principle) anything that the Mac can, then why were no ‘pro’ apps announced? Apart from the problem with the ‘pro’ moniker meaning different things to different users, ‘pro’ users were anticipating certain apps, like Final Cut Pro coming to the iPad (although some counter that apps like LumaFusion have evolved and are already available). While some enterprise-specific apps are available, like MS Office, most specialized apps are not. This will be up to specific third parties to make it so. Market forces dictate that, if and when the iPad Pro achieves a critical mass of adoption (more on that shortly), then competition will drive companies to overcome market inertia accordingly.
As for #3, at least one benchmark test suggests that iPadOS 15 beta possibly lifts the 5GB cap on apps, freeing developers to exploit the greater RAM capacity on the M1. Further tests will be forthcoming once iPadOS 15 is released. If true, it enables robust ‘pro’ app development (see #2 below).
#4, see Charlotte Henry’s link regarding Swift Playgrounds. Several developers on YouTube have commented similarly. However, as one recent MacVoices guest mentioned, the future for all app development is likely Swift and not Xcode. One indicator that this is likely the case is what The Verge piece points out, namely that with Swift Playgrounds developers can soon submit their apps directly to the App Store. This is a huge time-saver and a competitive advantage. In short, this tool may become both more powerful and the standard across the Apple platform, including the iPad. Adoption will assist in driving this forward.
As for #5, macOS on the iPad Pro, this would be contrary to Apple’s observed development philosophy. Apple is less likely to apply an older system to ‘upgrade’ a newer system than they are to continue improving that newer system, and macOS was never conceived or designed as a touch interface.
Next, we’ll look at macOS, iPadOS, and iPad Pro as well as our conclusions