A Mac Automation Schism

Thoughtful take by Jason Snell on the recent discussion around the idea that Shortcuts may be coming to the Mac and what that could mean for macOS automation. Snell imagines a scenario where Quick Actions, introduced last year with Mojave, could act as a bridge between old-school Mac apps and a new breed of Marzipan apps compatible (in theory) with Shortcuts only:

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.

As I argued on Connected a couple of weeks ago, I’m intrigued by the idea that a Mac version of Shortcuts could have built-in bridges for old automation tools (shell, AppleScript, Automator, etc.) to at least trigger those scripts from the new app. Quick Actions would be a great fit for this; in fact, I find the whole idea of Quick Actions is well suited the Files app on iOS as well.