Keyboard-first design on Windows - lessons from building a hotkey app

Jot is used mostly with the keyboard. You press a global shortcut, type, and press another to save. The mouse is optional. Designing for that changes more than which shortcuts exist; it changes where focus goes, what is visible, and how people learn the app.

Here are the lessons, in case you are building something similar.

1. Focus is the interface

In a keyboard-first app, where the cursor lands is the most important design decision on every screen. When the capture box opens, focus must already be in the text field. When it closes, focus must go back to the exact window you were in. Get either wrong and the app feels broken, even if every pixel is right. See giving the focus back.

2. Every action needs a key, and the key must be visible

Shortcuts nobody knows about do not exist. Jot shows small keycaps next to actions: Ctrl + Enter to save and close, Esc to dismiss, Ctrl + ↓ to peek at today. The keycap is a hint, not decoration, which is why the design system reserves the keycap shape for actual keys only.

3. Keep the shortcut set small

A keyboard-first app is tempted to bind everything. Resist. A handful of shortcuts people actually learn beats forty they look up once. Jot’s main surface has a short list:

• Ctrl + Shift + J: open the capture box (rebindable).
• Enter: save and keep the box open.
• Ctrl + Enter: save and close.
• Tab: switch Note, Todo, Meeting.
• Ctrl + ↓: peek at today’s todos.
• Ctrl + K: search everything.

4. Follow platform conventions

Esc closes. Tab moves forward. Ctrl + K is a common search shortcut in many apps. Where Windows has a convention, follow it, because users bring it from everywhere else. Microsoft’s guidelines for keyboard interactions in Windows apps are a useful reference.

5. Never trap the user

A global hotkey that cannot be changed, or a rebind that fails silently, can leave someone with no way into the app. Jot registers a new shortcut before releasing the old one, so a refused rebind keeps the working shortcut. A bare key without modifiers is refused outright, because it would swallow that key everywhere else. See choosing a global hotkey.

6. Keyboard-first is good accessibility

People who cannot use a mouse, or prefer not to, benefit directly. But keyboard-first is not the same as accessible: screen reader labels, focus outlines and contrast still need work. A visible focus indicator matters even in a minimal design.

7. The mouse still has to work

Keyboard-first does not mean keyboard-only. Clicking outside the overlay dismisses it, every button is clickable, and the app window is fully usable with a mouse. The keyboard path is the fast path, not the only path.

8. Measure the feel, not just the function

A keyboard app lives or dies on latency. If the box takes half a second to appear, people stop trusting the shortcut. Jot’s target is that the box is painted within 100 milliseconds of the keypress; the hundred-millisecond budget post explains the design constraints behind it, including the fact that the overlay window is created once and only shown and hidden.

Jot is on the Microsoft Store.

Jot is a quick-capture app for Windows: one hotkey, one line, back to what you were doing. What it is, or what is still unproven.