Raycast alternative: when a pie menu beats a command palette

This is not a post about replacing Raycast. Raycast is excellent. If you type fast and think in words, it is probably the most powerful launcher you can put on a Mac. I use it every day.

But I also use a radial menu every day, and the two do different things. The interesting question is not "which one wins?" but "which one is built for which shape of task?" Once you see the split, you stop trying to make one tool do both jobs and you stop feeling slow.

Naming vs pointing

Text launchers require you to name the thing. That is a small cognitive act, but it is real. Before you press Enter you have to recall the command, remember how it is spelled, and type at least two characters that disambiguate it from everything else.

Radial menus require you to point at the thing. No recall, no spelling. Your hand remembers the direction. It is the same reason a traffic light works: you do not read the word "stop," you react to the position.

Some tasks are shaped like names. Some tasks are shaped like positions. A calculator query — "1250 usd in eur" — is a name. A wedge marked "open Figma" is a position. Forcing either into the other shape is where people lose time.

What Raycast is genuinely better at

Stay on Raycast for anything you can articulate in two characters of text:

• Calculator and unit conversions. "250g in oz", "2h from now", "1.5 * 38". Faster than any menu.
• Quicklinks with parameters. Opening a Linear ticket by ID, a GitHub PR by number, a Notion page by title.
• Kill Process, Toggle Wi-Fi, Show IP, Clipboard History. Infrequent but named actions.
• AI chat and LLM extensions. Typing is the interface anyway.
• Emoji and symbol picker. You are already typing when you need it.
• Extensions. The ecosystem is enormous and good.
• Window management hotkeys. Fine and fast.

None of those fit a radial menu. You do not want a wedge that opens a calculator — you want to type the calculation. Raycast wins that entire category without a fight.

What a radial menu is genuinely better at

Swik is built for the opposite shape of task: a small number of things you do constantly, that you do not want to type, especially when your hand is already on the mouse.

• Your top 8–12 apps. You open them thirty times a day. Typing "figma" thirty times a day is thirty unnecessary taxes.
• Context actions. Start focus session. Start meeting mode. Toggle Do Not Disturb. One flick, done.
• When your hands are on the mouse. Reaching for the keyboard to type "cursor" is half a second of break. A mouse side button that opens a radial menu keeps both hands where they are.
• Recent documents. Swik can show the last few files you opened with a hovered app as an outer ring. You do not have to remember the filename.
• Profile-level context. Home Wi-Fi loads a different menu than office Wi-Fi. Raycast does not have a native concept of this.

Side by side

The subscription question, honestly

Raycast is free for the core launcher. The features that are gated behind Pro at $8 per month are themes, AI, notes, unlimited Clipboard History, and custom schedules. Whether that is worth it depends on whether you use the AI features — if you do, it is a reasonable price. If you only wanted themes, $96 a year is a lot to pay for cosmetics.

Swik is $9 one-time. That buys unlimited wedges, unlimited profiles, context triggers, the extended outer ring, Shortcuts.app integration, and every theme. There is no subscription tier and there is no plan to add one. If Raycast's subscription bothers you philosophically, Swik is a concrete answer for part of what Raycast does.

But it is not the whole answer. Swik does not do calculator, Kill Process, AI, Clipboard History, or extensions. If you want those, you either stay on Raycast or run both.

The "run both" case

This is the setup I actually use and recommend.

• Raycast triggered by a keyboard hotkey. This is for anything I can name — calculator, Kill Process, Linear tickets, Quicklinks, AI.
• Swik triggered by a mouse side button or a separate hotkey. This is for my top ten apps, context actions, and Shortcuts.

The two never overlap because they are reaching for different shapes of task. My hand is on the mouse when I want Figma; I press the side button, flick, done. My hand is on the keyboard when I want to compute a tip or kill a hung process; I press Cmd-Space-equivalent, type, done.

There is no conflict because there is no overlap. The mistake is trying to make Raycast handle the "one flick" case or trying to make Swik handle the "calculator" case. Each tool is worse at the other's job.

When Raycast is the right call

Stay on Raycast exclusively if:

• You are a keyboard-first user and rarely touch the mouse during focused work.
• You rely on Raycast extensions, AI, or Quicklinks with parameters.
• Most of what you launch is named, not spatial — calculators, URLs, ticket IDs, processes.
• You do not want a second tool on your machine.

When Swik is the right call

Add Swik alongside Raycast — or instead — if:

• You work with the mouse in one hand (design, video, browsing) and want launches without moving.
• You want context profiles that swap your menu by location or time.
• You want a one-time price for the specific "launch my top apps and Shortcuts" job.
• You have tried every command palette and still find yourself typing the same four app names a hundred times a day.

The honest recommendation: keep Raycast. Add Swik for the flick-shaped half of your workflow. The two together cost $9 plus whatever you already pay Raycast, and the split is clean.