Maya marking menus, but for your whole Mac

If you've modeled anything in Autodesk Maya in the last thirty years, you already know this gesture: hold space, a ring of tools fans out around your cursor, you flick toward the one you want, and release. No reading. No clicking. Just a flick in a direction your hand has memorized.

Maya calls them marking menus. They were formalized by Gordon Kurtenbach in his 1993 PhD thesis at the University of Toronto, built into Alias|Wavefront's PowerAnimator shortly after, and carried into Maya when Alias became part of Autodesk. They've been a fixture of professional 3D workflows since before most of the current generation of VFX artists could drive.

The rest of macOS has nothing like them.

Why Kurtenbach's research still matters

Kurtenbach didn't just build marking menus — he measured them. His experiments at the University of Toronto showed three things that have held up over three decades of replication:

Radial menus are faster than linear ones, on average. Fitts's Law is the mechanism: every wedge is the same distance from the cursor, so there's no "this item is farther down the list, so it's slower" penalty. All targets are equidistant.

Trained users develop what Kurtenbach called "expert mode." After enough repetitions, users stop reading the menu. They just flick in the right direction — pure muscle memory. The menu can even be suppressed entirely, and the gesture still works.

The expertise transfer is natural. Novices start by reading the menu. The menu teaches them the directions. Weeks later, they're experts, and they didn't have to consciously memorize anything. The interface itself is the training.

That last point is the quiet reason marking menus have survived so long in Maya. They meet you where you are. Day one, you hover and read. Day thirty, you don't.

What Maya actually did with the idea

In Maya, marking menus are everywhere and they're always contextual. Hold space over the viewport — you get a ring of modeling tools. Hold space in a different editor — you get a different ring. Hold shift-space and you get a different ring again. Right-click on a mesh — you get a marking menu for that object's tools specifically.

The really clever piece is that Maya's marking menus are user-customizable. You can define your own for your own toolset. Technical artists at studios ship internal marking menu libraries that bake their house rigging conventions straight into muscle memory. New hires inherit them on day one.

That's the part macOS has never had. A system-wide marking menu for the OS itself, customizable by the user, carrying the same hand-feel into Finder, Safari, Figma, Nuke, and Terminal.

The macOS gap

Go to any DCC (digital content creation) tool on Mac — Maya, Houdini, Blender, Cinema 4D, Nuke, Modo — and you'll find some version of the radial-menu pattern. Houdini has radial menus. Blender added them as a first-class feature in the 2.7x era. C4D has its "HUD" with adjacent ideas.

Then quit the app. The moment you're back at the desktop, the gesture is gone. Switching from Maya to Substance to a file browser and back means dropping in and out of the radial-menu world several times an hour. The OS itself has never spoken this language.

For a VFX or technical artist, this is jarring in a way that's hard to describe to someone who doesn't work this way. You've spent ten years training your hand to flick, and the moment you need to grab a screenshot or find a reference image, you're back to dragging a cursor to a menu bar like it's 1995.

Porting the pattern to the whole OS

This is what a system-wide radial menu like Swik is trying to close. Not to replace Maya's in-app marking menus — those know things about your current selection and tool mode that no OS-level tool ever will — but to give you the same gesture outside the DCC.

Hold a hotkey. Flick toward Nuke. Release. Nuke comes up. Hold the same hotkey. Flick toward your screenshot tool. Release. Screenshot tool.

It doesn't replace the deeper, context-aware marking menus inside each app. It doesn't try to. It just means the physical vocabulary of your hands — the flick, the release, the directional memory — now extends past the borders of whatever DCC you happen to be in.

A creative-workflow profile, concretely

Here's what a plausible creative-workflow setup looks like, using the eight cardinal directions plus a sub-menu:

Eight top-level wedges, two sub-menus. Every app in a production pipeline is a single flick away, or a flick-and-flick for the less common ones. On a second profile — triggered automatically when you're on the studio Wi-Fi, if your radial menu app supports context triggers — you could have a render-wrangling set of tools instead.

What this pattern can't do (yet)

An honest caveat: Maya's marking menus are powerful specifically because they're inside Maya. The radial menu knows what you have selected, what mode you're in, what kind of geometry you're hovering over. That depth of context isn't available to an OS-level radial menu — no third-party tool can know that you have an edge loop selected in Maya's viewport and adjust its wedges accordingly.

That means the pattern is complementary, not a replacement. You still need Maya's in-app marking menus for modeling operations. You still need Blender's pie menus for its mesh tools. What a system-wide radial menu adds is the connective tissue between those apps — the parts of your workflow that currently require moving your hand all the way to the Dock.

The real payoff is consistency. Your hands stop context-switching. The flick means the same thing whether you're in Maya or not. You don't need two different motor patterns for "pick a modeling tool" and "pick the next app I'm opening."

Why now

Kurtenbach's thesis came out in 1993. Maya has shipped marking menus for every version since. The research is well into its fourth decade. There's no good reason a VFX artist in 2026 should have to drop the gesture every time they leave Maya.

The tools to fix this finally exist. macOS's accessibility APIs have matured. A third-party app can now reliably draw an overlay, capture global input, and react to what's running in the foreground. Ten years ago the category barely worked on the Mac; now it does.

The pattern is proven. The research is settled. The software is possible. The only thing left is to actually use it.