Raycast’s design genius lies in building 2,500 extensions around just two keyboard shortcuts.
Press Enter to run a command; press Cmd+K to reveal more options. Learn those two rules once, and you’ll hardly ever need to learn how to use a feature again. You rarely see this kind of design power in the product world.
But while recording a podcast recently, I took another look at Raycast through the lens of a framework and found where its rules break down—often, that’s where a product’s structure reaches its limits.
The answer: AI.
Raycast was originally built around a rhythm of “appear, act, disappear”—quick, clean, and done in a few seconds. AI works very differently: you need to keep the conversation going, add files, adjust the tone, and build on previous responses. The first answer is a starting point, not the finish line.
So now Raycast has two doors: Quick AI lives in the command bar, while AI Chat lives in a separate window. Before asking a question, you have to figure out which door to use.
It seems like a small choice, but it quietly breaks the promise that you only have to learn once. Two keyboard shortcuts can’t support an interaction model like AI’s. That’s not a failure on Raycast’s part—it’s a structural question worth considering for anyone who builds products.
This podcast episode explores that observation, as well as the underlying principles of attention and cognitive load in *100 Things Every Designer Needs to Know About People*.
👉 https://redcircle.com/shows/936a3212-92e5-41c7-b6f9-39e3596adeb8/episodes/b0bf0eb9-9d32-4f02-9d28-1af2a2b9c243
Press Enter to run a command; press Cmd+K to reveal more options. Learn those two rules once, and you’ll hardly ever need to learn how to use a feature again. You rarely see this kind of design power in the product world.
But while recording a podcast recently, I took another look at Raycast through the lens of a framework and found where its rules break down—often, that’s where a product’s structure reaches its limits.
The answer: AI.
Raycast was originally built around a rhythm of “appear, act, disappear”—quick, clean, and done in a few seconds. AI works very differently: you need to keep the conversation going, add files, adjust the tone, and build on previous responses. The first answer is a starting point, not the finish line.
So now Raycast has two doors: Quick AI lives in the command bar, while AI Chat lives in a separate window. Before asking a question, you have to figure out which door to use.
It seems like a small choice, but it quietly breaks the promise that you only have to learn once. Two keyboard shortcuts can’t support an interaction model like AI’s. That’s not a failure on Raycast’s part—it’s a structural question worth considering for anyone who builds products.
This podcast episode explores that observation, as well as the underlying principles of attention and cognitive load in *100 Things Every Designer Needs to Know About People*.
👉 https://redcircle.com/shows/936a3212-92e5-41c7-b6f9-39e3596adeb8/episodes/b0bf0eb9-9d32-4f02-9d28-1af2a2b9c243