ShrtcutA radial launcher arranges choices in a circle around the pointer rather than in a vertical list. Every option sits the same short distance away and in a distinct direction, which makes selection a flick rather than a search. Radial menus have consistently outperformed linear ones in selection-time studies since the 1980s.
Why the circle is faster
The underlying reason is Fitts’s law, published in 1954: the time to hit a target depends on how far away it is and how big it is. It is one of the more reliably reproduced results in interface research, and it has an awkward consequence for menus.
A vertical list makes every item a different distance from the cursor. The first is close, the eighth is far, and the far ones are also thin — a menu row is generous horizontally and only about twenty pixels tall. So the items you use most are not necessarily the ones you can hit fastest, and the list gets worse as it grows.
A radial menu makes every item equidistant, and each wedge is a large angular target rather than a thin strip. Past a very short distance from the centre, you do not have to travel accurately at all — only in roughly the right direction. That is why a pie menu can be used without looking directly at it once the arrangement is familiar, and a list cannot.
Where radial menus actually fail
They do not scale. Eight wedges are comfortable and each is a 45-degree target. Sixteen halves that, and the precision required starts to undo the advantage that made the layout worth using. Nested rings solve the count and reintroduce the search you were avoiding.
They are also poor at text. A list can be scanned and typed against; a circle cannot be filtered by keyboard in any natural way. Anything that needs search — files, contacts, a large document library — belongs in a list, and Spotlight is the right tool.
And they require a pointer. A radial layout depends on direction, which means a mouse, trackpad, or touch. Keyboard-only users get nothing from it, which is a real accessibility limit rather than a preference.
This is the honest reason macOS does not use them: Apple ships one interface to everyone, and a pattern that excludes keyboard navigation and caps at roughly eight items is not one you can build a system menu bar on.
Where they have survived
The pattern persisted in exactly the places where the constraints do not bite. 3D and creative software has used pie menus for decades — Blender, Maya and Houdini all ship them — because the artist’s hand is already on the input device and the command set per context is small.
Games are the other stronghold. A weapon wheel is a radial menu, and it works because it is used under time pressure, by feel, with a fixed and small set of options. That is the same argument as the 3D software, arrived at independently.
What this means for app switching
Application switching happens to fit the shape well. The set is small — most people work in five to nine apps — it is used constantly, and it is used by feel rather than by reading.
It is also the case where the list form is weakest. Cmd-Tab is a horizontal list that grows with every app you open, ordered by recency, so the position of a given app changes between uses. There is nothing stable to learn, which is the specific problem a fixed radial arrangement removes.
The trade is real: you give up keyboard-only operation and you cap out around a dozen items. If those two things matter to you, a list is the better tool and no amount of Fitts’s law changes it.
Frequently asked questions
What is a radial launcher?
An app launcher that arranges its options in a circle around the pointer instead of a list. Each option sits the same distance away in its own direction, so selecting one is a short flick rather than a scan down a list.
Are radial menus really faster than lists?
For small, fixed sets of options, yes — this has been measured repeatedly since the 1980s. The advantage comes from every target being equidistant and angularly large. It disappears as the number of items grows.
Does macOS have a built-in radial menu?
No. macOS uses linear menus throughout. Radial menus require a pointer and work poorly beyond about eight items, which makes them unsuitable as a system-wide pattern.
How many items should a radial menu have?
Eight or fewer is the usual guidance, giving each item a 45-degree target. Beyond twelve the wedges become narrow enough that the precision required cancels out the speed advantage.