When you run a new app for the first time you’re now increasingly likely to undergo an onboarding experience, explained by Apple as giving the user “a high-level view of your app or game”. The term is taken from its use in the management of new employees in the US, and equivalent to what much of the rest of the English-speaking world refers to as induction.
Far from that idealistic vision, in most onboarding for Mac apps, that phase is dominated if not overwhelmed by a series of skirmishes with privacy settings, without which that app might be non-functional.
Apple’s advice to developers is at best naïve. Onboarding is seen as optional: “People want to start using your app or game immediately after first launching it, whether they participate in an onboarding flow or skip it.”
But a little further down, perhaps it could prove essential: “If your app or game needs access to private data or resources before it can function, consider integrating the permission request into your onboarding flow. In this scenario, making the request during your onboarding flow gives you the opportunity to show people why your app or game needs their permission and the benefits of granting it. Otherwise, present a permission request when people first access the specific function that relies on private data or resources.”
Skipping onboarding of some Mac apps could thus render them incapable.
For many apps this brings a tautology of intent. I was looking for an app to archive my email, it’s named Mail Archiver, yet the first thing it asks me during onboarding is whether I really want to give it access to my emails. Similarly, a backup utility that’s intended to maintain copies of all the files on my Data volume asks me during onboarding whether I really want to give it access to the whole of that volume. I then have to be taken out of the app to Privacy & Security settings to complete those, sometimes several times, and often have to quit the app altogether so those new settings can be applied, before opening the app a second time.
Yet Apple envisages onboarding as being “fast, fun, and optional”, the exact opposite of what it has become for so many Mac apps.
With a little effort, this could be so different. Given that privacy is so important, and transparency the order of the day, why can’t an app display a single window in which all its potential privacy issues are addressed, informing even the most pernickety user of the choices they must make, and from there setting privacy access directly, without dumping the user into System Settings? This could surely be managed securely by macOS, much in the way that it handles the authentication process.
There’s a strange asymmetry here, in that few of Apple’s apps require any onboarding, nor do they comply with the rules it enforces on all others. macOS gives Time Machine full disk access without seeking the user’s consent, but third-party products are required to obtain Full Disk Access before they can work. Of the 44 apps that I have given access to Files & Folders on my Mac, only three are Apple’s: Terminal with Full Disk Access, Pages with iCloud Drive, and FileMaker Pro with Documents. The latter two could be accidental for all I know. If good privacy protection requires full transparency, that should surely be applied equally, no matter who the developer or how their app is delivered.
Apple has recently recognised the threat to privacy protection posed by AI agents, and intends tightening controls in macOS 27.3. Those should bring some improvements, but inevitably increase complexity and in practice that may defeat their purpose. In some cases, that will result in even longer and more tortuous onboarding.
Siri and AI aren’t controlled in Privacy & Security settings, and Siri’s settings include all apps by default, offering instead an exclusion list the user has to build for themselves. While Private Cloud Compute does give the user strong assurance that Apple protects their privacy, we know that using AI provides a lot of personal data for context. While that’s a good thing, it demonstrates how smooth Apple can make privacy controls when it wants.
I’m all in favour of having robust and effective privacy controls, but they must be designed and implemented for humans, ordinary users, who want their onboarding to be “fast, fun, and optional”.
