A command palette is what we're basing our UX rebuild over at https://grey-wing.com https://grey-wing.com, so I can point out some additional benefits, drawback

A command palette is what we're basing our UX rebuild over at https://grey-wing.com https://grey-wing.com, so I can point out some additional benefits, drawbacks and fixes: A command palette when implemented correctly, can also strike a balance between older users and power users. It doesn't hold power users back, but the verbose nature of the instructions and command (no more undecipherable icons and strange UI interactions) can also be easier for older, less techy users - IF implemented well with a lot of testing. There is still a lack of discoverability with a command palette. Our solution has been to include commonly used commands, and most popular commands alongside, as well as introducing some new ones intermittently. One more problem is context. More complicated commands may be harder to grok or conversely very long for users to remember. The UNIX solution is switches, which is short but hard to remember (https://xkcd.com/1168/ https://xkcd.com/1168/), and the alternative is long sentences which is hard to parse, perhaps too long, and has too much variation to be reliable. Finally, they're also a great way to discover what paths your users would like to go down but can't. It's hard to understand what button they couldn't find or what label they didn't understand from a traditional UI, even with extensive user interviews and analytics. With an omnibox, each failed search is a point of information to you.