By Jason Snell
May 1, 2019 3:21 PM PT
Last updated July 27, 2020
Are we headed for a Mac automation schism?
Note: This story has not been updated since 2020.
User automation is important. Giving users the power to eliminate repetitive tasks and connect apps together in ways the app designers never anticipated helps harness the power of computers to make our lives easier. Even people who aren’t comfortable with building automation systems themselves can benefit from work created by others. User automation makes computing devices more powerful and their users more efficient.
The Mac is currently at the start of a pretty dramatic transition. This year, the platform will be flooded with apps that are based on the iOS app development system, UIKit, using a system that everyone calls Marzipan because Apple hasn’t given it a name. (My guess is that Apple won’t brand it at all, and will just call it “UIKit for macOS.”
Part of this transition affects user automation. macOS has a bunch of different system-level user automation technologies of various ages, but none of them work with iOS and Apple has shown no intention of changing that now. AppleEvents, AppleScript, and Automator already feel like legacy technologies that are maintained minimally to keep up compatibility, but they don’t feel like the future.
For years, iOS seemed to be a wasteland of user automation, but determined app developers discovered ways their apps could interact, most notably by embedding data in URLs—yep, the same strings of text you use to visit webpages—and passing them back and forth. Apple seemingly endorsed this technique when it bought Workflow, a popular third-party iOS automation app, and renamed it Shortcuts last summer. At the same time, Apple connected iOS automation to Siri through a feature called Siri Shortcuts, which fits right into existing systems already used by developers.
So what happens when iOS apps comes to the Mac this fall? It seems impossible that Apple will allow them to be controlled by AppleScript and Automator. On iOS, they can be controlled by Shortcuts. Does that app make the move to macOS? According to 9to5Mac’s Guilherme Rambo, it might, and Siri Shortcuts will.
Will “classic” Mac apps1 get the ability to be controlled via Shortcuts, too? Or will there be a schism between the two different classes of apps? (It’s not great for Mac users if there are two different kind of apps that live side by side and are supposed to be the same but are secretly “Type A” and “Type B” apps with different functionality. That happened a lot in the early days of Mac OS X and it was not great.)
And what about Automator and Shortcuts, two apps with similar approaches and aims? Do they live awkwardly side by side on macOS, each addressing some percentage of a user’s apps while ignoring the rest?
I’ve got to think Apple won’t leave the developers of “old-style” Mac apps high and dry. My hope is that Apple will provide developers of old-school Mac apps with some tools to integrate their apps with whatever automation system comes along with the new stuff, presumably Shortcuts.
If the goal is to avoid a complete schism, Apple could allow users to build their own bridges between apps by adding “Run shell script” and “Run AppleScript” commands within Shortcuts. While it might strike you as impossible that Apple would allow this, the truth is that the barn door is already open and the horse is long gone. Shortcuts for iOS has an action that lets you run scripts on a remote server via SSH. If that feature ends up on the Mac, it’s over—all a user will have to do is tell the shortcut to connect to
What’s more, one of macOS’s shell commands is
osascript, which—you guessed it—executes AppleScript scripts. Which means I can already run AppleScript and command-line commands on my Mac via my iPad. So why shouldn’t I be able to do so from my Mac? Doesn’t make sense.
Siri Shortcuts gateway?
Then there’s Siri Shortcuts, which 9to5Mac says are almost certainly coming to macOS. Since this is a system based on iOS technology, it would seem like classic Mac apps and features might be entirely left out. It’s a break-up that doesn’t need to happen, so long as the proper bridges are built.
Something funny happened in macOS Mojave. Apple actually brushed off some very old Mac OS X technology, Services, and gave it a rebrand as Quick Actions. Quick Actions are commands you can find in Quick Look previews, the Finder’s new Gallery view, and on the Touch Bar. Some are pre-built by Apple, but users can add their own by saving Automator actions as Quick Actions.
I have no idea what prompted Apple to bubble up Automator actions into more places in the macOS interface with Mojave, but Quick Actions strikes me as a pretty good companion to Siri Shortcuts. Imagine a scenario where apps originating on iOS can support Siri Shortcuts via the same methods they use on iOS. Now imagine that Siri Shortcuts can also use Quick Actions as a source for potential commands. Quick Actions are contextual, those old-school Mac apps can bring their own Quick Actions to the party, and users can build their own Quick Actions to do whatever they want. It would be a simple way to bridge the gap between the two different app types that Mac users will be using together, at least for a while.
I don’t know if Apple’s planning to do this, but it’s hard not to imagine macOS 10.15 causing a pretty dramatic class division between apps, and that’s bad for the user experience. Some weirdness is inevitable when you’ve got different apps using different System Folders, APIs, and the rest. But the more bridges that exist—ones that let the different apps work together for the benefit of users—the better.
It’s just the beginning
I have a million questions about the future of user automation on Apple’s platforms, beyond just the scope of the changes in macOS 10.15. Are URL schemes really the future of inter-application communication, or is Apple working on a new system that’s a successor to AppleEvents that will offer a more robust pathway than a giant string of plain text? Is Shortcuts going to gain more low-level capabilities on both platforms? Will third-party automation utilities like Keyboard Maestro be able to control UIKit apps effectively?
In the end, I’m not as concerned with how user automation is preserved on macOS as I am concerned that it is preserved. Shortcuts is a remarkably powerful app, and even URL schemes can be richer than you might think—though they’re definitely inelegant. The Mac can help push automation technology forward across all of Apple’s platforms, if Apple wants to go in that direction. But whatever happens, it’s clear that iOS and macOS are going to face the future of user automation together, not separately.
- We are probably about to enter an era where all the Mac apps built using AppKit, the development system that’s “native” to macOS, are going to start being referred to as “classic” Mac apps, and the new UIKit apps are going to be called “new” Mac apps. ↩
If you appreciate articles like this one, support us by becoming a Six Colors subscriber. Subscribers get access to an exclusive podcast, members-only stories, and a special community.