The Most User-Friendly LMS Should Not Make You Cry: We Built a ⌘K Command Palette So Admins Can Stop Hunting for Settings

You know the setting exists. You configured it three months ago. You just cannot remember whether it lives under Course Settings, or Site Administration, or Plugins, or that one tab nested under "More..." that you only find by accident. So you click around. Again. Every single time.

If that paragraph made you sigh in recognition, you already understand why I am writing this. I am Amir, I have been an LMS engineer for thirteen years, and I got tired of building (and using) software that makes smart people feel stupid. So at Cubite we shipped the thing every modern tool from Linear to Slack to GitHub treats as table stakes: a command palette.

Hit ⌘K (Ctrl+K on Windows or Linux), type what you actually call the thing, and land on it. This post is my argument that Cubite is the most user-friendly LMS for admins and students, and unlike every "easiest LMS to use" listicle on the internet, I am going to prove it with one shipped feature instead of a pile of adjectives.

It is not just a you-problem. It is a category problem. Brandon Hall Group found that 44% of companies are actively considering replacing their LMS, up 16% since 2015 (via eLearning Industry / Brandon Hall). People are not leaving because their LMS lacks features. They are leaving because using it hurts.

"User-friendly" is the most overused, least proven word in LMS marketing

Go search "easiest LMS to use" or "most intuitive LMS." You will get a wall of articles that say "intuitive," "clean," "simple," "modern" and show you nothing. Not one of them demonstrates a mechanism. They assert a vibe and move on to the pricing table.

Here is my founder thesis: ease of use is not a vibe. It is measurable. It is the number of clicks to finish a task. It is whether a brand-new admin can find a setting without a training session. It is whether a student can reach their course without getting lost. You can count those things. You can ship against them. If you cannot point at the concrete thing that lowers those numbers, you are just decorating a claim.

So let me be honest up front about what I am and am not claiming. I am not going to tell you Cubite is objectively, universally THE most user-friendly LMS, as if that were a measured fact handed down from a lab. That is exactly the kind of empty claim I am criticizing. What I am going to do is argue it, show you one concrete feature you can try yourself, and give you an honest look at who else in this category got there first. You decide.

The real problem: buried menus, too many clicks, and training just to find a setting

I want to be specific, because the pain is specific. When I read public reviews of legacy LMS platforms, the same phrasings repeat independently from teachers, IT directors, students, and L&D people across different review sites. That consistency is the signature of a structural UX problem, not a few cranky users having a bad day.

A few verbatim lines, all about Moodle, all public:

Read that last one again. Training. To navigate. Not to teach, not to build a course, just to find where things are. The frustration is not about missing capability. It is about not being able to reach the capability you already have.

The path is the bug

Here is the cleanest example of buried settings I have ever seen, straight from a Moodle.org forum thread. Enrolment methods are:

"A lot of clicks for them to remember." That is the whole bug in one sentence. The expectation is that you, the human, will hold the menu tree in your head.

Here is the reframe that changed how I think about the entire category: you should not have to memorize the path to a setting. The path is the bug. Moodle's own answer to this is partly to hand you obscure keyboard shortcuts you have to commit to memory (press "g" then "s" for settings, "g" then "u" for users, per Moodle's admin shortcut docs) and a settings keyword search page at admin/search.php that has no shortcut to open it and is not a fuzzy palette. That admin/search.php search is real and useful, honestly the closest thing in the legacy world to searching iPhone Settings. But it treats the symptom. If I have to memorize a hotkey to reach a menu, I have just traded one memory burden for another, and I still have to know the search page exists and go to it.

And if you go searching "find settings in LMS" or "where is this setting," you only get how-to docs that recite the click path: Site Administration, then Plugins, then Manage tools. Nobody answers the actual wish underneath the query, which is simply: let me search.

What a command palette is, and why it became table stakes everywhere except the LMS

So what is a command palette? Plain version: it is one keyboard shortcut (⌘K on Mac, Ctrl+K on Windows and Linux) that opens a search box you can use to jump to any feature or setting by typing what you call it. That is it.

The cleanest analogy is the one already living in your pocket. On your iPhone, you do not navigate four levels into Settings to find Wi-Fi or Bluetooth. You swipe down, type a word, and tap the result. You do not need to know or care that Apple filed it under Settings, then Display, then some sub-screen. The search box absorbs the memory work so your brain does not have to. (Apple Support / iPhone Life describe exactly this: swipe, type, tap, you are there.)

This pattern is everywhere in modern software. Linear, Vercel, GitHub, Slack, Raycast, and WordPress all ship ⌘K palettes. It has quietly become a baseline expectation for any serious tool. Why? Because keyboard-first, search-driven navigation lowers cognitive load. You offload the entire menu tree out of your head and into a search box. You think about what you want, not where it lives.

The LMS category is roughly a decade behind on this, which is exactly why it was the first thing I wanted to fix. That gap is the whole opportunity, and it is what makes a genuinely user-friendly LMS rare in this space.

So we built ⌘K into the Cubite admin: type what you call it, land on it

Here is the announcement, and here is exactly what it does. No hand-waving.

Open it. Hit ⌘K on a Mac or Ctrl+K on Windows or Linux from anywhere in the admin, or click the "Search..." button at the top of the sidebar. Escape closes it (or steps you back out of a picker). It is mounted globally, so it is on every admin screen.

Search what you call it. It searches a static index of exactly 302 entries covering every admin feature, section, setting, action, report, and tool. Every entry carries a pile of synonym keywords, so you can find things by the words you actually use, not by the official menu label. The comment in the source file literally says "like iPhone Settings search," because that is the behavior we built, not a slogan we bolted on afterward. Type "pricing," "learners," "payments," "certificate expiry," or "webhooks" and the right thing surfaces.

Results are typed and ranked. Each result is labeled by kind: "Go to," "Setting," "Action," "Report," or "Tool," so you know what you are about to do. Matching is deterministic and predictable: exact label match beats prefix, beats substring, beats keyword match, beats all-tokens-present. With an empty box it shows a curated landing list of the common shortcuts you reach for most.

Drill down to the exact tab. This is my favorite part. 119 of the 302 entries (49 course entries plus 70 site entries) are entity-aware. Select one and it asks you to pick a course or a site, then deep-links you to the precise tab. Not the course page. The exact tab. For example:

• /admin/courses/{id}?tab=learners
• /admin/courses/{id}?tab=details&sub=access
• /admin/sites/{domain}?tab=payments
• /admin/sites/{domain}?tab=integrations§ion=webhooks

You do not land on a generic page and hunt. You land on the sub-tab. And if you only manage one course or one site, it skips the picker entirely and takes you straight there. No menus, no mouse.

It is scoped to you, on the server. You only ever search your own courses, sites, and settings. Live course matches come from an authenticated API that refuses to answer without a session and returns everything only to true global admins. Everyone else sees only the courses they instruct or that belong to sites they administer, plus the sites they actually manage. Role gating goes further: entries like Organizations, Audit, and Contracts only appear for the roles allowed to use them.

It is accessible and on-brand. Arrow keys move the selection, Enter opens it, the dialog uses role="dialog" and aria-modal, body scroll locks while it is open, and the shortcut listens on the physical "K" key so it survives non-US keyboard layouts. It is styled entirely with your tenant's DaisyUI theme tokens, so it matches your brand in light or dark mode instead of a hardcoded look, and it floats above all the admin chrome through a portal.

What it is not, on purpose

Now the honest scope, in plain founder voice, because I would rather you trust me than oversell you. This is deterministic keyword and synonym search. It is not AI, semantic, or natural-language search. There are no embeddings, no fuzzy spell-correction, no command history or favorites. And it navigates you to where an action lives; it does not run the delete, the enrollment, or the certificate issuance inline from the palette. It searches your courses by name, your sites by name, and the 302 feature entries. It does not full-text search learner records or content bodies. That restraint is deliberate. Deterministic search is fast and predictable. You always know what it will do, which is exactly the property a tool you use fifty times a day needs.

Who else got there: an honest look at the LMS command-palette landscape

I am not going to tell you nobody else does this, because that would be a lie you could debunk with one screenshot. I audited a dozen of the biggest LMS admins for a true ⌘K palette. Here is the honest map.

Most do not have one. Canvas, Blackboard, Open edX, TalentLMS, Teachable, Thinkific, and Absorb leave you hunting through sidebars and nested menus. Some have a basic course or user search box, which is not the same thing as a jump-to-anything palette. Instructure's own admin tips concede that searching for a user or course in Canvas takes too many clicks. Absorb has an open customer feature request titled "Enable keyboard shortcuts on admin portal" (LMS-I-311), which tells you the capability is both absent and wanted.

Credit where it is genuinely due, stated plainly. LearnWorlds ships a native ⌘K / Ctrl+K palette that, per their own product page, lets you jump to any feature, setting, course, or learning activity instantly. LearnDash inherits one for free, because it lives inside wp-admin and WordPress 6.9 brought the core Command Palette across the whole admin in late 2025. So we are not the first, and I will say that clearly.

Moodle gets partial credit: its admin/search.php is a keyword search of site settings, the nearest thing to iPhone-Settings search in that ecosystem, but there is no shortcut to open it and it is not a fuzzy palette. Docebo (Harmony) and 360Learning both have global search bars that can reach admin pages, and Docebo even lets you type the name of a menu to jump to it, but they are header search boxes with no documented opening shortcut, not keyboard-driven palettes.

So this is not a "nobody does it" story. It is a "the category is a decade behind and only a couple caught up" story. The difference for Cubite is that we did not bolt on a checkbox feature to match a spec sheet. We built the admin around search because the pain is real, sourced, and repeated by thousands of frustrated users.

Why a user-friendly LMS matters for students too, not just admins

Honest boundary first: the command palette is an admin, manager, and instructor tool. Students do not get it. I am not going to pretend otherwise.

But the principle behind it, reduce cognitive load, do not make people memorize where things are, is the same fight on the learner side. And the evidence says learners feel the same pain:

When the people who build courses can move fast and find everything, the courses learners receive are cleaner and better organized. So the same discipline drives our recent, founder-led work on the learner surface (and I will frame this honestly as in-progress on our develop branch, not a GA guarantee): a rebuilt single-panel courseware reading and exam experience with a collapsible content rail, active-row highlighting, and a full-screen focus mode for exams; per-tenant DaisyUI theming so every site keeps its own brand; and reusable catalog layouts an admin can switch on from an Appearance picker instead of commissioning a custom build.

Here is the claim, earned rather than asserted: a genuinely user-friendly LMS has to be friendly on both sides of the login. The command palette is one concrete, shipped piece of evidence that we mean it on the admin side, and the courseware work is how we are carrying the same discipline to the learner side. We are building toward that deliberately, and I would rather show you the work than just say the word "intuitive" at you.

Try it: hit ⌘K

Ease of use is provable, and the proof is a keystroke.

Open a Cubite admin, press ⌘K (or Ctrl+K), and type the one setting you can never find in your current LMS. Watch it land you on the exact tab. That is the entire argument, and you can run it yourself in about three seconds.